Security & Identity
Authentication, authorization, user identities and session management in the APPNETOS Core.
APPNETOS provides shared security services while keeping application and administration identities separated by runtime context. User and group persistence is optional and is enabled through context-specific class mapping.
Context-specific identity
The app context uses mapped application user and group collections, while the
admin context uses separate administration collections. Administration collections
are not accessible from the application context by default.
If no user collection is mapped, the application has no user system. If users are mapped but no group collection is available, authentication can operate without group-based permissions. Applications that do not require identities or permissions can omit both mappings.
Authentication and session lifecycle
The standard ForceSignIn workflow validates credentials, completes any required two-factor challenge and redirects after successful authentication. The next request initializes the authenticated user and resolves their groups. The session controller manages persistence and expiration independently of PHP's native session mechanism.
Expired-session cleanup through a dedicated worker in appnetos-platform is planned.
The Core already exposes session cleanup operations.