Nuxeo Server

Authentication and User Management

Updated: December 26, 2016 Page Information Edit on GitHub

Functional Overview

Default Authentication Mode - Login Page

By default user gets authenticated on the Nuxeo Platform by filling username / password on the login page. That information is checked against the one stored in database, or transmitted to the configured identity provider. If the username or the password is invalid, a message is sent to the user. Default password of user Administrator is Administrator, if you didn't change anything. Password of each user can be changed either by the user himself, or by the administrators in the Admin Center. The password complexity is checked against a regexp that can be changed.

Other Authentication Protocols

The login page is not the only way to authenticate a user against the Nuxeo Platform. Some other protocols can be used, sometimes requiring to install an additional module (See related pages):

  • Basic authentication (built-in)
  • Token (Nuxeo Platform proprietary) (built-in)
  • oAuth2 (built-in)
  • SAML2 (Addon)
  • 2 Steps, with SMS for instance (Addon)
  • Trusted (for instance requests coming from that particular IP address do not need to validate authentication) (built-in)
  • Open ID (Addon)
  • Kerberos (built-in)
  • CAS / CAS2 (built-in)
  • NTLM (built-in)
  • Redirecting to a remote identity management solution then having the user fall back authenticated to the Nuxeo Platform (SSO servers, Open Id, Portals, ...) (built-in or addon, depending on the case).

Thanks to the pluggability of the authentication layer (see the Implementation section), it is easy to write a custom authentication protocol when necessary.

Compatible IdM Solutions

Default configuration checks identity against a Java implementation inside the Nuxeo Platform. By configuration and addition of some modules, and following the above list of supported protocols, the Nuxeo Platform can be integrated with various identity providers:

Unauthenticated Access

Anonymous User

A configuration allows to have the user automatically logged in as a user called "anonymous", for which some specific permissions have been set. The name of that user is configurable, and allows to simulate an "unauthenticated" access to the Nuxeo Platform. The users having the Manage permission on a repository can reference that anonymous user as any other user and declare some folders and documents accessible to everybody.

See the page Anonymous Authentication.

Unauthenticated URLs

It is also possible to define a list of URL patterns for which no authentication is required (so not using the anonymous user either). That way you can say that a specific website generated by the platform is available without authentication while the other pages served by the platform sends the user to the login page. When browsing those URLs, no principal is created, which means no access to the repository can be done.

User and Groups Provisioning

Storage Options for Users and Groups

The UserManager is the component in charge of managing users and groups. The default implementation stores them in the Nuxeo Platform via the "directory" abstraction: one directory for users and one for groups.

Directories can use either:

  • An SQL implementation (thus storing users and groups on the underlying RDBMS)
  • An LDAP implementation
  • A Nuxeo Platform repository implementation (Users and Groups are then "documents")
  • A custom implementation for calling remote webservice is also sometimes used.

It is possible to reference a meta-directory that would be the result of the merge of several directories, a mix of different implementations (LDAP, SQL...) and different hosts. For instance part of the users can be handled in the corporate LDAP server, and part in the Nuxeo Platform database. This situation is referenced as multidirectory in the documentation.

Features Available around Users and Groups Management

When users are dealt through directory abstraction (so 90% of the cases), the Nuxeo Platform provides user interfaces (and REST APIs) for handling:

  • User CRUD by administrators
  • User password management by administrator
  • Groups CRUD and assignment by administrator (including management of sub-groups)
  • User profile management by the user
  • Password management by the user
  • User and groups search (for filling a metadata, assigning an ACL, selecting a specific user in a search filter,...)
  • User invitation: A Nuxeo addon adds to default Nuxeo Platform UI and services for inviting by email a future user that would not have yet an account in the platform

For more information, please see Managing users and groups.

Virtual Users

It is also possible to declare a set of "virtual" users, that are defined in the application although they don't exist on the user directory the instance is plugged to.

User Profile

A set of properties is stored by default for any user in the Nuxeo Platform:

  • username
  • first name
  • last name
  • company
  • email

Those properties can come from the IdM the Nuxeo Platform is integrated to. To extend the list of available fields for a user, see the page How to add New Fields to The User Profile or Group Profile.

Authentication Schemes Use

You may want to use other authentication protocols and / or identity providers than LDAP/Active Directory. Most of the time, an "authentication plugin" has to be configured. The Nuxeo Platform provides some by default, but you sometimes have to install a specific addon.

In any case, you have to configure the "authentication chain".

Contribute an XML extension from the following content. Adapt the authenticationChain element content with the list of plugins you want to use.

  <extension
    target="org.nuxeo.ecm.platform.ui.web.auth.service.PluggableAuthenticationService"
    point="chain">
    <authenticationChain>
      <plugins>
        <plugin>BASIC_AUTH</plugin>
        <plugin>ANONYMOUS_AUTH</plugin>
        <plugin>THE_PLUGIN_I_WANT_TO_USE</plugin>
      </plugins>
    </authenticationChain>
  </extension>

The Nuxeo Platform will use the plugins in the order they are chained. First attempt for each plugin will be to retrieve credentials (see implementation for a better understanding). If no credential is found, it will try to call the showLoginPrompt method for each of the plugin up until one is successful.

All the available authentication plugins and instructions for installation or links to their documentation are listed in below dedicated pages.

Customization

Customizing the Login Page

You can customize the login page using Nuxeo Studio (background picture, colors, logo).

Integrating with a Webservice Based Identify Provider

You can build a custom directory that will wrap your webservice.

You can use the Nuxeo directory connector sample as a starting point.

3 months ago Solen Guitter Fix links, formatting issues, add related pages, rename pages
3 months ago Solen Guitter reorganize authentication page
3 months ago Solen Guitter review authentication
4 months ago Funsho David Review authentication doc
4 months ago Andrew Goodricke Add content-review-lts2016 to labels
4 months ago Kevin Leturc NXP-19481: Update MarkLogic page to detail how to configure range element indexes
7 months ago Solen Guitter 23 | dd details on section SSO with Portal
9 months ago Manon Lumeau 22
a year ago Manon Lumeau 21
a year ago Solen Guitter 20
a year ago Alain Escaffre 19
a year ago Alain Escaffre 18
a year ago Alain Escaffre 17
a year ago Alain Escaffre 16
a year ago Solen Guitter 15
a year ago Solen Guitter 14 | Fix TOC style in Install & Config tab
a year ago Solen Guitter 13 | Shorter titles in install&config tab
a year ago Solen Guitter 12
a year ago Solen Guitter 11 | Fix some anchor links
a year ago Solen Guitter 10 | Fix some fomat issues
a year ago Solen Guitter 9
2 years ago Alain Escaffre 8
2 years ago Alain Escaffre 7
2 years ago Alain Escaffre 6
2 years ago Alain Escaffre 5
2 years ago Alain Escaffre 4
2 years ago Alain Escaffre 3
2 years ago Manon Lumeau 2
4 years ago Solen Guitter 1
History: Created by Solen Guitter