com.mohiva.play.silhouette.impl.authenticators
The authenticator ID.
The linked login info for an identity.
The last used timestamp.
The expiration time.
The time in seconds an authenticator can be idle before it timed out.
Custom claims to embed into the token.
The Type of the generated value an authenticator will be serialized to.
The Type of the generated value an authenticator will be serialized to.
Custom claims to embed into the token.
Discards an authenticator.
Discards an authenticator.
The result to wrap into the com.mohiva.play.silhouette.api.Authenticator.Discard result.
A com.mohiva.play.silhouette.api.Authenticator.Discard result.
Discards an authenticator.
Discards an authenticator.
The result to wrap into the com.mohiva.play.silhouette.api.Authenticator.Discard result.
A com.mohiva.play.silhouette.api.Authenticator.Discard result.
The expiration time.
The authenticator ID.
The authenticator ID.
The time in seconds an authenticator can be idle before it timed out.
Checks if the authenticator isn't expired and isn't timed out.
Checks if the authenticator isn't expired and isn't timed out.
True if the authenticator isn't expired and isn't timed out.
The last used timestamp.
The linked login info for an identity.
The linked login info for an identity.
Renews an authenticator.
Renews an authenticator.
The result to wrap into the com.mohiva.play.silhouette.api.Authenticator.Renew result.
A com.mohiva.play.silhouette.api.Authenticator.Renew result.
Renews an authenticator.
Renews an authenticator.
The result to wrap into the com.mohiva.play.silhouette.api.Authenticator.Renew result.
A com.mohiva.play.silhouette.api.Authenticator.Renew result.
An authenticator that uses a header based approach with the help of a JWT. It works by using a JWT to transport the authenticator data inside a user defined header. It can be stateless with the disadvantages that the JWT can't be invalidated.
The authenticator can use sliding window expiration. This means that the authenticator times out after a certain time if it wasn't used. This can be controlled with the idleTimeout property. If this feature is activated then a new token will be generated on every update. Make sure your application can handle this case.
The authenticator ID.
The linked login info for an identity.
The last used timestamp.
The expiration time.
The time in seconds an authenticator can be idle before it timed out.
Custom claims to embed into the token.
https://developer.atlassian.com/static/connect/docs/concepts/understanding-jwt.html
http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html#Claims