Added the possibility to give administrator rights to the user group at the portal via LDAP;

Updated the rules for LDAP users.

Version 2.5.1

Release date: 04/07/2018

LDAP

Fixed the Server internal error error when using the groups enclosed inside each other in the AD (bug #37414).

Single Sign-on

Fixed the issue when the user data between the Service Provider and the portal was transferred via HTTP only, even when HTTPS was enabled.

Version 2.4.0

Release date: 01/13/2018

Single Sign-on

Fixed the Invalid ssoConfig error which occurred when the link to the IdP contained the question mark '?', e.g.: IdP Single Sign-On Endpoint URL: https://accounts.google.com/o/saml2/idp?idpid=777777;

Fixed the Invalid authentication token error which prevented from adding a user to the portal using the AD FS, in case the + or - characters were present when sending the encrypted data.

Version 2.3.0

Release date: 12/15/2017

General

Added the changelog for Control Panel and link to it;

Fixed the bug when JWT parameters were not sent when updating Document Server(bug #36270);

Fixed the bug when Audit Trail heading was present at the login history page (bug #36026);

The current machine is now checked for being linked with the domain name for multiple portals.

LDAP

Fixed the bug with the LDAP Domain not found error which occurred if the DN record had no DC records (the users with Sun/Oracle DS were affected); now if the LDAP domain could not be specified, the LDAP domain will acquire the unknown value or the ldap.domain value from the web.appsettings.config configuration file;

Fixed the bug with the Sizelimit Exceeded error when trying to get more than 1000 users from the Active Directory;

Increased the login speed with the Group Membership setting enabled;

Added additional logging;

Fixed the bug with LDAP operation hanging when using Mono v5.2.0 and older;

Fixed the bug with the error when trying to login using the email address entered in the fields different from the Mail Attribute;

Fixed the bug occurring in the enclosed groups, when the users were displayed not in all groups.

Version 2.2.0

Release date: 10/31/2017

General

Added the documentserver-prepare4shutdown.sh script launch when updating the document-server for the correct edited document saving.

LDAP

Dramatically changed LDAP integration, migrated to the single library for the work with LDAP (Novell.Directory.Ldap.NETStandard, Nuget, MIT);

Login and email are now split into two separate fields;

Added the support for big data;

Increased the work speed via the LDAP protocol (the connection to the server and receiving the data is now made once per session, added the limits when only a certain number of results is necessary, fixed the slow login for bit data, removed the sorting out used to find the SID parameter);

Instead of re-creating a user with an unknown SID but an existing email the data is updated;

Added the attempt to save the correct UserName/Login in case a similar one is already taken on the portal.

Single Sign-on

Added the AD FS support;

Replaced the Single Sign-on link at the authorization page with the customizable button, added the button customization to the SSO setting of the Control Panel.

Version 2.1.0

Release date: 07/03/2017

HTTPS

Added the support of letsencrypt service for the domain certificate generation.

Single Sign-on

Added the new sso.auth service;

Added the new SSO settings page;

Added the support for Shibboleth.

Version 2.0.0

Release date: 05/25/2017

General

The Control Panel migrated from MVC to Node.js.

Version 1.6.0

Release date: 12/05/2016

LDAP

Added LDAP synchronization for users and groups when saving the settings, after login and using the Sync button;

Changed email formation for LDAP users;

Fixed the problem of creation of users with invalid emails;

Fixed the problem of duplicate users;

Added icons and hints to the users in the list for the admin;

Blocked for editing the user profile fields imported using LDAP;

Added the real LDAP password saving to the database during login in case LDAP Auth is disabled, now the LDAP users will become common portal users when LDAP Auth is disabled;

Added new API Settings method - Sync LDAP;

Added new translations;

Bug fixes.

Version for Windows

Made changes at the Update page for the Control Panel for Windows;

Updates are performed using the downloaded installation packages for each module.

The current installed component version numbers are obtained via API request to the Community Server.

The new versions available for download are obtained via the request to the https://download.onlyoffice.com/install/windows/updates.txt file, where all the latest component version numbers and links for their download are stored in the JSON format.

Introduction

Single Sign-on (SSO) is a technology that allows users to sign in only once and then get access to multiple applications/services without re-authentication.

If a web portal includes several large independent sections (forum, chat, blogs etc.), a user can undergo the authentication procedure within one of the services and automatically get access to all other services without entering credentials several times.

SSO is always ensured by the joint operation of two applications: an Identity Provider and a Service Provider (hereinafter referred to as "IdP" and "SP"). ONLYOFFICE SSO implements the SP only. A lot of different providers can act as an IdP, but this article considers the Active Directory Federation Services (AD FS) implementation.

System requirements

The system requirements include the following software which has been tested and proved to be working correctly with ONLYOFFICE SSO:

Windows Server 2008 R2, Windows Server 2016;

AD FS version 3.0 or later.

Preparing ONLYOFFICE Enterprise Edition for the SSO setup

Install ONLYOFFICE Enterprise Edition v9.5 for Docker or any later version with the SSO support.

Add a domain name, e.g., myportal-address.com.

On your portal, go to the Control Panel -> HTTPS, create and apply the letsencrypt certificate for the traffic encryption (to enable HTTPS on your portal).

To verify that AD FS has been started correctly, open the received link in a web browser. The xml should be displayed or downloaded. Copy the link to the metadata xml: it will be required at the next step.

Configuring ONLYOFFICE SP

Make sure that you are signed in as an Administrator to your ONLYOFFICE Control Panel and click the SSO tab.

You can only register one enterprise Identity Provider for your organization on the ONLYOFFICE portal.

Enable SSO using the Enable Single Sign-on Authentication switcher and paste the link copied from the AD FS into the URL to Idp Metadata XML field.

Press the button with the upward arrow to load the IdP metadata. The ONLYOFFICE SP Settings form will be automatically filled in with your data from the AD FS IdP.

In the Custom login button caption field, you can enter any text instead of the default one (Single Sign-on). This text will be displayed on the button used to login to the portal with the Single Sign-on service at the ONLYOFFICE authentication page.

In the NameID Format selector, choose the following value: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.

In the IdP Public Certificates \ Advanced settings section, uncheck the Verify Logout Response Signature option, as AD FS does not require that by default.

Now you need to add certificates to the SP Certificates section. You can generate self-signed certificates or add any other certificates.

in the New Certificate window, switch the Use for selector to the signing and encrypt option, as AD FS IdP is automatically configured to verify digital signatures and encrypt data.

You should get nearly the same result:

In the SP Certificates \ Advanced settings, uncheck the Sign Logout Responses, as AD FS does not require that by default.

It is not necessary to adjust the Attribute Mapping form, as we will set these parameters in the AD FS IdP later.

Click the Save button. The ONLYOFFICE SP Metadata section should be opened.

Verify that our settings are publicly available by clicking the Download SP Metadata XML button. The XML file contents should be displayed.

Copy the link to the ONLYOFFICE SP metadata from the SP Entity ID (link to metadata XML) field and go to the machine where AD FS is installed.

Configuring AD FS IdP

In the Server Manager, open Tools -> AD FS Management,

In the AD FS Management panel, select the Trust Relationships > Relying Party Trusts. Click the Add Relying Party Trust... option on the right. The Add Relying Party Trust Wizard opens,

In the wizard window, select the Import data about the relying party published online or on a local network radio button, paste the previously copied link to the ONLYOFFICE SP metadata into the Federation metadata address (host name or URL) field and click the Next button,

In the Display name field, specify any name and click the Next button,

Select the I do not want to configure multi-factor authentication settings for this relying party trust at this time option and click the Next button,

Select the Permit all users to access this relying party option and click the Next button,

Check the resulting settings and click the Next button,

Leave the default option unchanged and click the Close button,

A new window opens. At the Issuance Transform Rules tab, click the Add Rule... button,

Select the Send LDAP Attributes as Claims option from the Claim rule template list and click the Next button,

Type in any name in the Claim rule name field. Select the Active Directory option from the Attribute store list and fill in the Mapping of LDAP attributes to outgoing claim types form according to the table below. When ready, click Finish.

LDAP Attribute (Select or type to add more)

Outgoing Claim Type (Select or type to add more)

Given-Name

givenName

Surname

sn

E-Mail-Addresses

mail

Telephone-Number

mobile

Title

title

physicalDeliveryOfficeName

l

In the Edit Claim Rules window, click the Add Rule... button once again, select the Transform an Incoming Claim option from the Claim rule template list and click the Next button,

Type in any name in the Claim rule name field and select the following options from the lists:

Incoming claim type: mail,

Outgoing claim type: Name ID,

Outgoing name ID format: Email

When ready, click the Finish button.

You should get nearly the same result:

If logout from AD FS does not work, it's recommended to add a Custom Claim Rule replacing {portal-domain} with your SP domain and changing {ad-fs-domain} to your IdP domain:

Checking the work of the ONLYOFFICE SP with the AD FS IdP

Logging in to ONLYOFFICE on the SP side

Click the Single sign-on button (the caption may differ if you have specified your own text when configuring ONLYOFFICE SP). If the button is missing, this means that SSO is not enabled.

If all the SP and IdP parameters are set correctly, we will be redirected to the AD FS IdP login form:

Enter the login and password of the AD FS IdP account and click the Sign in button.

If the credentials are correct, we will be redirected to the main page of the portal (the user will be created automatically if missing, or the data will be updated if changed in the IDP).

Profiles for users added with SSO authentication

The possibility to edit user profiles created using the SSO authentication is restricted. The user profile fields received from the IdP are disabled for editing (i.e. First Name, Last Name, Email, Title and Location). You can edit these fields from your IdP account only.

The figure below shows the Actions menu for an SSO user:

The following figure shows an SSO user profile opened for editing:

The users created using the SSO authentication are marked with the SSO icon in the user list for the portal administrators:

Download
Host on your own server
Available for
Docker, Windows and Linux