Class PendingSamlAuthentication
java.lang.Object
com.revetsec.saml.PendingSamlAuthentication
An engine-created pending SAML login. Place its sealed form in a Secure, HttpOnly, SameSite=None
browser cookie for a cross-site POST ACS. A sealed cookie can be replayed in concurrent callbacks;
the assertion replay cache still prevents releasing the same assertion twice. An atomic pending
store is required when the application needs authoritative single consumption of the login itself.
- Since:
- 1.0.0
-
Method Summary
Modifier and TypeMethodDescriptionReturns the app-owned hint sealed into this request, when supplied.Returns the expiration of this login attempt.Returns the opaque RelayState handle.Returns the generated request ID.saveToResult(@NonNull PendingSamlAuthenticationStore store, @NonNull StateSealer sealer, @NonNull String context, @NonNull BrowserBinding browserBinding, @NonNull Duration remaining) Seals and saves this login under a browser-bound context.toSealedForm(@NonNull StateSealer sealer, @NonNull String context) Seals this pending login under the SAML-specific type and exact application context.toString()Redacts the pending identifiers.
-
Method Details
-
toSealedForm
Seals this pending login under the SAML-specific type and exact application context. A valid pending record may exceed the configured sealer limit; this method then throwsIllegalArgumentException. Persist successfully before delivering the request.- Parameters:
sealer- active and verification sealing keyscontext- fixed application-selected cookie context- Returns:
- the sealed value for a browser-bound cookie
- Since:
- 1.0.0
-
saveToResult
public @NonNull SamlPendingSaveResult saveToResult(@NonNull PendingSamlAuthenticationStore store, @NonNull StateSealer sealer, @NonNull String context, @NonNull BrowserBinding browserBinding, @NonNull Duration remaining) Seals and saves this login under a browser-bound context. A possibly completed save returns INDETERMINATE; callers must not assume that retrying is safe. If the complete encoded record exceeds the configured sealer limit, returns UNAVAILABLE without calling the store or drawing sealing entropy. Shorten configuration or options before retrying; no pending state was saved. Invalid contexts remain argument errors.- Parameters:
store- atomic pending storesealer- active and verification sealing keyscontext- application-selected store namespacebrowserBinding- browser-specific secretremaining- positive operation budget- Returns:
- the storage outcome
- Since:
- 1.0.0
-
getRequestId
Returns the generated request ID.- Returns:
- request ID
- Since:
- 1.0.0
-
getRelayStateHandle
Returns the opaque RelayState handle.- Returns:
- handle
- Since:
- 1.0.0
-
getExpiresAt
Returns the expiration of this login attempt.- Returns:
- expiry
- Since:
- 1.0.0
-
getApplicationData
Returns the app-owned hint sealed into this request, when supplied.- Returns:
- optional application data
- Since:
- 1.0.0
-
toString
-