Skip to content

Latest commit

 

History

History
113 lines (81 loc) · 4.3 KB

README.md

File metadata and controls

113 lines (81 loc) · 4.3 KB

Nonce Authenticator Plugin Example

Quality Availability

SSO Navigation

In some setups, environmental limitations prevent OpenID Connect Single Sign On (SSO) from working.
In these cases, the user will first authenticate in a source application.
When navigating to a target application, re-authentication will be required, with a suboptimal user experience.
The nonce authenticator pattern provides a solution to the double login problem.

Mobile Use Case

A common use case for this pattern is when navigating from a mobile app to a web app.
Different cookie jars may be used for SSO cookies, resulting in a double login by default.

Nonce Authenticator

This plugin uses the Nonce Token Issuer from the Java SDK.
This enables the source application to issue a nonce and use it to bootstrap SSO in the target application.
The target application uses the nonce, with is validated in a single sign on flow.

Security Flow

The source OAuth client must first extend its audience to include the nonce issuing endpoint.
The endpoint format is [BASE URL] + [Anonymous Authentication Endpoint] + [Authenticator Name]. The client can post its ID token to this endpoint, to create a nonce:

curl -X POST 'https://idsvr.example.com/authentication/anonymous/nonce1' \
    -H 'Content-Type: application/x-www-form-urlencoded' \
    --data-urlencode 'token=eyJraWQi...'

Next, the target OAuth client can be navigated to, using a nonce as a URL query parameter.
This value can only be used once, is very short lived, and is used immediately by the target application:

https://www.example.com?nonce=OFiicYQJYY2phWnD5nFMflid5Du82ycW

The target application then performs its own OpenID Connect redirect, which is guaranteed to use SSO:

http://idsvr.example.com/oauth/v2/oauth-authorize
    ?client_id=web-client
    &redirect_uri=http%3A%2F%2Fwww.example.com%2F
    &response_type=code
    &code_challenge=l9QIPE4TFgW2y7STZDSWQ4Y4CQpO8W6VtELopzYHdNg
    &code_challenge_method=S256
    &state=NlAoISfdL1DxPdNGFBljlVuB1GDjgGARmqDcxtHhV8iKNYu6ECS2KOavDHpI3eLN
    &scope=openid%20profile
    &acr_values=urn:se:curity:authentication:nonce:nonce1
    &login_hint_token=OFiicYQJYY2phWnD5nFMflid5Du82ycW
    &prompt=login

The following additional OpenID Connect parameters are used in this redirect:

Parameter Description
acr_values Forces the nonce authenticator to be used
login_hint_token Supplies the nonce for validation
prompt Prevents nonce authentication being bypassed via SSO cookies

The target OAuth client then authenticates silently, with no user prompts.
The target OAuth client then receives its own set of tokens, with its own scopes and claims.

Building the plugin

The plugin is built by issuing this command:

mvn package

This will produce JAR files in the target directory:

nonce-authneticator-*.jar
jose4j-*.jar

Deploy these JAR files to your instances of the Curity Identity Server, in a plugins subfolder.
The plugin group authenticators.nonce can be replaced with any other arbitrary name of your choice:

$IDSVR_HOME/usr/share/plugins/authenticators.nonce/*.jar

Configuration

The plugin requires the following settings:

Property Example Value
Audience https://idsvr.example.com/authentication/anonymous/nonce1
Issuer https://idsvr.example.com/oauth/v2/oauth-anonymous
JWKS Endpoint https://idsvr.example.com/oauth/v2/oauth-anonymous/jwks
Nonce Validity Seconds 120

Website Documentation

See the following resources on the Curity website.
The code example provides an end-to-end solution that can be run on a standalone computer:

More Information

Please visit curity.io for more information about the Curity Identity Server.