- Created by Sathya Ramanathan, last modified by Jennifer Perkins on Feb 18, 2021
Updates to SAML SSO
As of FIleCloud Version 19.1, the ability to limit users to SSO by group is available.
As of FIleCloud Version 19.2, FileCloud can detect an SSO email and automatically redirect the user to the corresponding IDP provider with prefilled login information for the user.
As of FIleCloud Version 19.3, you can override the default SSO port.
As of FileCloud Version 20.3.2, to achieve high availability, you can configure FileCloud to support multiple memcache servers.
You can use SAML SSO to control the authorization and authentication of hosted user accounts that can access FileCloud Web based interface.
- SAML is an XML based open standard data format for exchanging authentication and authorization data between parties.
- FileCloud supports SAML (Security Assertion Markup Language) based web browser Single Sign On (SSO) service
- FileCloud acts as a Service Provider (SP) while the Customer or Partner acts as the identity provider (IdP). FileCloud SAML SSO service is based on SAML v2.0 specifications.
In the following section, to display more information, click on a topic.
The following process explains how the user logs into a hosted FileCloud application through customer-operated SAML based SSO service.
- The user attempts to reach the hosted FileCloud application through the URL.
- FileCloud generates a SAML authentication request. The SAML request is embedded into the URL for the customer’s SSO Service.
- FileCloud sends a redirect to the user’s browser. The redirect URL includes the SAML authentication request and is submitted to customer’s SSO Service.
- The Customer’s SSO Service authenticates the user based on valid login credentials.
- The customer generates a valid SAML response and returns the information to the user’s browser.
- The customer SAML response is redirected to FileCloud.
- The FileCloud authentication module verifies the SAML response.
- If the user is successfully authenticated, the user will be successfully logged into FileCloud.
When the IdP successfully authenticates the user account, FileCloud (SP) authentication module verifies that the user account exists in FileCloud.
- If the user account does not exist in FileCloud, then a new user account is created and the user is logged into FileCloud.
Normally SSO works in the web browser when the user logs on to the User Portal.
- FileCloud clients such as FileCloud Sync and Drive do not support Single Sign On directly.
- To support SSO, read SSO on desktop Clients
Note
- Integrate Auth0 SSO with Filecloud
- Integrate Azure AD with FileCloud
- Integrate Azure AD with FileCloud - Classic UI
- Integrate Azure AD with FileCloud - New UI
- Integrate Centrify with FileCloud
- Integrate JumpCloud with FileCloud
- Integrate Okta with FileCloud
- Integrate OneLogin with FileCloud
- Integrate ADSelfSevice Plus with FileCloud
Setting Up and Configuring Certificates when Upgrading SSO
SSO Configuration Steps
In order to successfully configure SAML SSO, the following steps must be followed.
In the following section, to display more information, click on a step.
Configuring the Apache server requires you to add the Alias directive to the simplesaml.php configuration file.
Pre-requisite: The mcrypt module must be installed on the FileCloud Server.
- In Windows, it should be installed by default.
- In Linux, if mcrypt is not installed, it must be installed
To add the Alias directive:
Use the following table to understand the typical entries in Linux and windows.
You can change these settings if the FileCloud is installed under a different WEB ROOT Folder.
OS | Instructions |
---|---|
Windows |
|
Linux |
|
To set the SSO type in FileCloud:
Log into the FileCloud Admin Portal.
In the left navigation panel, click Settings.
Select the SSO tab.
In Default SSO Type, select SAML.
Active Directory Federation Services (ADFS) Support
When SAML SSO Type is selected and ADFS is enabled in FileCloud:
- FileCloud will act as a Service Provider (SP)
- FileCloud also acts as a claims aware application.
As a claims-aware application, FileCloud:
- Accepts claims in the form of ADFS security tokens from Federation Service
- Can use ADFS claims to support Single Sign On (SSO) into FileCloud
To specify the identity claims that are sent to the FileCloud refer to the IdP Configuration section below.
When ADFS is used, the IdP (Identity Provider) in these instructions refers to Active Directory Federation Server.
To configure IdP settings in FileCloud:
Log into the FileCloud Admin Portal.
In the left navigation panel, click Settings.
Select the SSO tab.
In Default SSO Type, verify it is set to SAML.
Set oher parameters according to your IdP settings.
Use the following tables to understand the IdP settings.
FileCloud Parameters | IdP Settings | ADFS as IdP Data can be obtained from Federation Metadata |
---|---|---|
IdP End Point URL | Identity Provider URL | Identity Provider URL (Entity ID) |
Idp Username Parameter | Identifies the Username (must be unique for each user)
NOTE: The username must be unique. If username sent by Idp is in email format, the email prefix will be used for username. The email prefix in this case must be | Identifies the Username (must be unique for each user) value: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn or upn |
IdP Email Parameter | Identifies the email of the user (must be unique) Default value: mail | Identifies the email of the user (must be unique) http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress or emailaddress |
IdP Given Name Parameter | Identifies the given name of the user Default value: givenName | Identifies the given name of the user. http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname or givenname |
IdP Surname Parameter | Identifies the surname of the user Default value: sn | Identifies the sur name of the user http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname or surname |
IdP Log Out URL (Optional) | URL for logging out of IdP | URL for logging out of IdP |
Limit Logon to IdP Group (available in FileCloud Version 19.1 and higher) | IdP Group Name
| IdP Group Name
|
Show the IdP Logon Screen | Identifies which Logon screen the user will see:
| Identifies which Logon screen the user will see:
|
IdP Meta Data | Identity Provider Metadata in XML Format | Federation Metadata in xml format |
SSO Error Message (Optional) Added in FileCloud 20.1 | Custom error message that appears when a signin is invalid. Enter in HTML format. In a multiple IDP environment, this is the error message for the default IDP. To include a message specific to each IDP, include the parameter <MESSAGE>. See Integrating Multiple IDPs for help configuring multiple IDPs with error messages specific to each one.. | Custom error message that appears when a signin is invalid. Enter in HTML format. In a multiple IDP environment, this is the error message for the default IDP. To include a message specific to each IDP, include the parameter <MESSAGE>. See Integrating Multiple IDPs for help configuring multiple IDPs and error messages specific to each one. |
Allow Account Signups Added in FileCloud 20.1 | When TRUE, during the login process, if the user account does not exists, a new FileCloud user account is created automatically. | When TRUE, during the login process, if the user account does not exists, a new FileCloud user account is created automatically. |
Automatic Account Approval Added in FileCloud 20.1 | This setting works with the Allow Account Signups setting to determine:
See Integrating Multiple IDPs for help configuring multiple IDPs with automatic account approval settings specific to each one. | This setting works with the Allow Account Signups setting to determine:
See Integrating Multiple IDPs for help configuring multiple IDPs with automatic account approval settings specific to each one. |
Enable ADFS | No | Yes |
User login token expiration match Idp expiration | If enabled the user token expiration will be set based on Idp expiration settings If not enabled user token expiration will be set based on FileCloud Session Timeout Default: No (Not enabled) | If enabled the user token expiration will be set based on ADFS expiration settings If not enabled user token expiration will be set based on FileCloud Session Timeout Default: No (Not enabled) |
Show the Idp Login Screen | If enabled, automatically redirect user to Idp log-in screen. | If enabled, automatically redirect user to Idp log-in screen. |
Log Level | Set the Log mode for the SAML Calls. Default Value: prod (Do not use DEV for production systems) | Set the Log mode for the SAML Calls. Default Value: prod (Do not use DEV for production systems) |
Use the following URL (Entity ID) to register FileCloud as an SP with IdP or ADFS. The URL below also provides the metadata of the FileCloud SP.
There are two ways users get redirected to the Identity Provider’s SAML Single Sign On page from the FileCloud Web browser interface.
- Using the Single Sign-On link on the Login Page.
- Using Direct URL to go to customer’s SAML SSO page.
In order to display the Single Sign On link on the FileCloud Web browser user interface:
- Show SSO on the Customization > General > Login screen must be checked.
- Show Login Options on the Customization > General > Login screen must also be checked.
On clicking the Single Sign-On link on the login page, the user is redirected to the SAML SSO Service web page.
In order to skip the login page, go to cloudconfig.php file under the <PATH TO FileCloud WEBROOT>/config folder and add the following line.
define("TONIDOCLOUD_SSO_DIRECT", "1");
The value 1 implies to skip the FileCloud login page and display the SSO login page directly. Value 0 implies, show the FileCloud login page.
Note: This redirect is only effective if the user specifies a domain name rather than a full URL.
Starting with Version 19.3, FileCloud supports skipping the login page when the user accesses FileCloud with a domain name or with a full URL. Instead of the above line, enter:
define("TONIDOCLOUD_SSO_DIRECT_ONLY", "1");
Starting with Version 20.1, FileCloud supports skipping the login page when the admin accesses FileCloud with a domain name or with a full URL. Enter:
define ("TONIDOCLOUD_SSO_DIRECT_ONLY_ADMIN", "1");
Starting with FileCloud 13.0, FileCloud admin interface also supports Single Sign On. SSO can be used to login into admin interface for all users who have an account with the Identity Provider.
As an alternate option, users can completely skip the FileCloud login page and directly go to the SSO login page when coming to http://yourfileclouddomain URL.
In order to skip the login page, go to cloudconfig.php file under the <PATH TO FileCloud WEBROOT>/config folder and add the following line.
define("TONIDOCLOUD_SSO_DIRECT_ADMIN", "0");
The value 1 implies to skip the FileCloud login page and display the SSO login page directly. Value 0 implies, show the FileCloud login page.
Issue | Details |
---|---|
Avoid Open Redirect | FileCloud may be vulnerable to an open redirect when SSO is implemented.
This can be avoided by configuring the following setting:
|
Restrict the Available Admin Login Resources | The FileCloud Admin Portal can possibly allow 2 administrative login interfaces:
This can be avoided by changing the log level to "PROD" in SSO settings under settings in FileCloud admin interface. This will disable the SSO admin page under simpleSAML. The password to the SSO admin page under /simpleSAML can be changed under 'auth.adminpassword' key in <FileCloud WEB ROOT>/thirdparty/simplesaml/config/config.php |
Use the following table to read about issues that you may encounter and how to resolve them.
Issue | Solution |
---|---|
FileCloud is hosted behind a Proxy | When FileCloud is hosted behind a proxy server, SAML will not automatically work. Go to <FileCloud WEB ROOT>/thirdparty/simplesaml/config/filecloudconfig.php Add Proxy Server Information here. Format is as follows user:password@yourproxyserverurl.com define("TONIDOCLOUD_SAML_PROXY", "ADD PROXY INFO HERE"); |
System Timezone Settings | After setting SAML log level to DEV. Log file will be created under <FileCloud WEB ROOT>/thirdparty/simplesaml/log/simplesamlphp.log SimpleSAML_Error_Exception: Error 2 - strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. Solution: date.timezone setting must be set explicitly in php.ini |
FileCloud is hosted behing a reverse proxy | When FileCloud is hosted behind a proxy server, SAML will not automatically work. Go to <FileCloud WEB ROOT>/thirdparty/simplesaml/config/config.php set the base url to 'baseurlpath' => 'http(s)://YOURFILECLOUDOMAIN/simplesaml/' |
Debug page login | https://YOURFILECLOUDDOMAIN/simplesaml/module.php/core/frontpage_welcome.php |
FileCloud in HA (High Availability) envrionment with multiple servers | In this scenario, SimpleSAML will most likely not work with default configuration and will require to run Memcache to manage the session. Go to <FileCloud WEB ROOT>/thirdparty/simplesaml/config/config.php set the store.type => memcache and set 'memcache_store.servers' => array( where 'localhost' must be replaced with IP of memcache server as appropriate. |
Autofill Username or Email on the IDP screen when configuredTONIDOCLOUD_SAML_DOMAINS_ALLOWED | When autofill will only work when username or email address is sent through POST from the FileCloud login page to IDP. Therefore, ensure that the IDP metadata accepts requests through only POST. For example, if the Idp Metadata contains the following 2 similar lines, remove the Redirect and only have the POST <md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://mailinator-raja.okta.com/app/mailinatororg747392_myidp_1/exkgimvocj18Exx9g4x6/sso/saml"/> |
Override the default SSO port
In FileCloud Versions 19.3 and higher, you can override the default SSO port.
To override the default port:
- Open cloudconfig.php:
Windows Location: XAMPP DIRECTORY/htdocs/config/cloudconfig.php
Linux Location: /var/www/config/cloudconfig.php Add the following line:
define("TONIDOCLOUD_SSO_FULLURL_OVERRIDE", "https://filecloud.test.com");
Use multiple memcache servers
In FileCloud Versions 20.3.2 and higher, you can use multiple memcache servers with SAML SSO to achieve high availability.
To use multiple memcache servers:
- Open cloudconfig.php:
Windows Location: XAMPP DIRECTORY/htdocs/config/cloudconfig.php
Linux Location: /var/www/config/cloudconfig.php - Add the following lines, including a hostname for each of the memcache servers.
In this example, the IP addresses of the servers are 79.97.83.70 and 79.97.83.71.
function SSO_MEMCACHED_SERVERS() { return [ [ ['hostname' => '79.97.83.70'], ['hostname' => '79.97.83.71'], ], ]; }
- No labels