Package com.okta.sdk.resource.model

Class LogAuthenticationContext

java.lang.Object
com.okta.sdk.resource.model.LogAuthenticationContext
All Implemented Interfaces:
Serializable
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2024-09-23T08:35:59.300824-05:00[America/Chicago]", comments="Generator version: 7.8.0") public class LogAuthenticationContext extends Object implements Serializable
All authentication relies on validating one or more credentials that prove the authenticity of the actor's identity. Credentials are sometimes provided by the actor, as is the case with passwords, and at other times provided by a third party, and validated by the authentication provider. The authenticationContext contains metadata about how the actor is authenticated. For example, an authenticationContext for an event, where a user authenticates with Integrated Windows Authentication (IWA), looks like the following: ``` { \"authenticationProvider\": \"ACTIVE_DIRECTORY\", \"authenticationStep\": 0, \"credentialProvider\": null, \"credentialType\": \"IWA\", \"externalSessionId\": \"102N1EKyPFERROGvK9wizMAPQ\", \"interface\": null, \"issuer\": null } ``` In this case, the user enters an IWA credential to authenticate against an Active Directory instance. All of the user's future-generated events in this sign-in session are going to share the same `externalSessionId`. Among other operations, this response object can be used to scan for suspicious sign-in activity or perform analytics on user authentication habits (for example, how often authentication scheme X is used versus authentication scheme Y).
See Also: