Interface SessionProvider
- All Known Subinterfaces:
SessionProvider.CookieSessionProvider
,SessionProvider.EmptySessionProvider
,SessionProvider.JwtSessionProvider
For example assume that FIDO UAF is used as second factor with nevisAuth. In this case the user must first provide a password and then authenticate using FIDO UAF. When the user provides the password, nevisProxy will generate a cookie that is used to track the authentication session. The HTTP client authenticating must provide this cookie on all the HTTP requests that are sent while authenticating. Thus, the cookie (associated with the authentication session) must also be provided during the FIDO UAF authentication, the HTTP client must authenticate to obtain some authorization tokens (HTTP cookies, JWT, etc.). The client can access the protected resource (the FIDO UAF registration endpoints in this case) by providing these authorization elements.
Currently cookie and JWT based session management is supported.
-
Nested Class Summary
Modifier and TypeInterfaceDescriptionstatic interface
An HTTP cookie based session provider.static interface
AnSessionProvider
providing no session information.static interface
An JWT based session provider.