Nuxeo Server

Using OpenID / OAuth2 in Login Screen

Updated: November 13, 2017 Page Information Edit on GitHub

You can use any OpenID / OAuth2 identity provider in the authentication chain. A Nuxeo addon, OpenID Authentication, is available to make this possible.

The default behavior is to display a sign-in button per identity provider to start the authentication challenge, then building the expected UserIdentificationInfo with the provided UserInfo.

By default, the username resolved with the identity provider user information must be in the user directory to allow it to access the Nuxeo Platform.


The Nuxeo addon OpenID Authentication enables you to use OpenID Connect, the identity layer on top of the OAuth 2.0 protocol, and so to use OAuth2 providers as Identity providers.

This addon requires no specific installation steps. It can be installed like any other package with nuxeoctl command line or from the Update Center.


Declaring a New IdentityProvider in Nuxeo

<extension point="providers" target="org.nuxeo.ecm.platform.oauth2.openid.OpenIDConnectProviderRegistry">
        <description>Login using your Google account</description>

This first contribution only defines the provider, but not the client name or client secret to prevent them to be in the base contribution file.

Setting up the Authorized Redirect URI

In your identity provider configuration, set up the Authorized Redirect URI to the Nuxeo server. For a local Nuxeo instance using GoogleOpenIDConnect for instance this would be:

  • With JSF UI:
  • With Web UI:

Appending Provider Secrets

Set up the following values in your nuxeo.conf depending on your target provider. You can only set the ones you need.

# Github

# Google

# Google+

# LinkedIn

# Amazon Connect

# Facebook Connect

UserInfo Mapping

Each identity provider has its own way to handle user identity in his UserInfo endpoint. You may need to add your own mapping class.

You just have to extend the org.nuxeo.ecm.platform.oauth2.openid.auth.OpenIDUserInfo class with the expected fields. Do not forget to set it in your provider contribution.

You can take a look to our implementation like or org.nuxeo.ecm.platform.oauth2.openid.auth.DefaultOpenIDUserInfo .

Username Resolution

By default we provide two username resolvers.

One is based on the email field (org.nuxeo.ecm.platform.oauth2.openid.auth.EmailBasedUserResolver). The second one that handles username by concatenating the provider id and the user's subject field (org.nuxeo.ecm.platform.oauth2.openid.auth.StoredUserInfoResolver).

You can easily add your own by extending theorg.nuxeo.ecm.platform.oauth2.openid.auth.UserResolver class.

Others Parameters

You have the possibility to change some behaviors by adding the following parameters in your nuxeo.conf:

  • nuxeo.skip.oauth.token.state.check (default: false): Whether to skip checking if the provider response contains the correct OAuth2 state. Default value if recommended for security.
  • nuxeo.oauth.auth.create.user (default: false): Create user on request if not exists.

Other OAuth / OPenID Related Documentation
4 days ago manonlumeau Added content-review-lts2017 label
a month ago manonlumeau NXDOC-1346-FT review screenshot
a year ago Manon Lumeau 11
3 years ago Julien Carsique 10
3 years ago Julien Carsique 9
3 years ago Julien Carsique 8
3 years ago Julien Carsique 7
3 years ago Solen Guitter 6 | Add screenshot
3 years ago Solen Guitter 5
3 years ago Arnaud Kervern 4
3 years ago Arnaud Kervern 3
3 years ago Arnaud Kervern 2
3 years ago Arnaud Kervern 1
History: Created by Arnaud Kervern