Provides the elements required to run an operation in a session.
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.
Provides the elements required to run an operation in a session.
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.
See