Oracle Weblogic Server (MOSC)

MOSC Banner

Mitigate the effect of clock skewing with WebLogic SAML Authentication Provider

in Oracle Weblogic Server (MOSC) 1 commentAnswered

Oracle WebLogic Version 12.2.1.4.220329.

The SAML 2.0 standard describes an optional security feature, token validity in terms of Conditions inside the SAML Assertion (NotBefore/NotOnOrAfter). Validation is implemented in the Oracle WebLogic Service Provider (SP) implementation, WebLogic SAML Authentication Provider. However, in real world networks with best-effort clock synchronization (based on NTP) a situation can occur where the host running the Identity Provider has a time slightly ahead of that of the host running the Service Provider ('clock skewing'). Thus, if the Identity-Provider sets NotBefore to 'now', the generated token has a NotBefore date that is ahead of the current time on the service provider.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center