Skip to main content

Authentication & Login

The APIs mentioned in this section are REST APIs that may be called in authentication flows, for example by a standard AuthState, or by a Groovy script executed by a nevisAuth ScriptState.

It is typically not required to call these APIs directly, as the main way to interact with Nevis ID is through Federation.

These APIs are primarily considered to be internal. You can call these APIs from a nevisAuth ScriptState with Groovy, but they are rarely exposed to the internet for consumption by external clients.

The subsections Login and Login info mention APIs of the nevisIDM component. This is obvious as the request paths all start with /nevisidm/.

These APIs can be involved in authentication flows, but are usually only called when there is no standard pattern for your use case.

The subsection Session Management describes the /management/session API of the nevisAuth component. This API is also internal and used in a session termination use case provided by nevisAdapt.

Endpoints in this section

PathMethodsPurpose
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/password/loginPOSTAuthenticate with a password
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/device-password/loginPOSTAuthenticate with a device password
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/context-password/loginPOSTAuthenticate with a context password
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/otp/loginPOSTAuthenticate with an OTP
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/otp/challengePOSTGenerate an OTP challenge
/nevisidm/api/auth/v1/{clientExtId}/users/{userExtId}/recovery-codes/loginPOSTAuthenticate with a recovery code
/nevisidm/api/core/v1/{clientExtId}/users/{userExtId}/login-infoPOSTUpdate user's login information
/nevisidm/api/core/v1/{clientExtId}/users/{userExtId}/bulk-login-infoPOSTBulk update login information
/management/sessionDELETETerminate sessions by attribute
/management/session/{id}DELETETerminate a session by session ID