For security reasons, Federation Services and any kind of single sign-on (SSO) support is only allowed in server or private cloud licenses of SpreadsheetWEB.
The Security Assertion Markup Language (SAML) version 2.0 has been established in 2005 as the dominant standard for cross-domain web single sign-on (SSO) in the enterprise space. SAML 2.0 defines several roles for parties using single sign-on:
- The user authenticates (logs in) to the identity provider (or IdP) which is typically hosted (e.g. windows active directory, facebook, twitter, etc.).
- User can then access a resource through one or more service providers such as www.spreadsheetweb.com (abbreviated as SP, and known as relying parties) without needing to log in to each service provider.
There are two ways of establishing SSO:
- Identity Provider Initiated Single Sign-on (IdP-initiated) SSO
- With IdP-initiated login, there’s typically a link on the company intranet that users can use to directly access SpreadsheetWEB.
- Service Provider Initiated Single Sign-on (SP-initiated) SSO
- For giving access to SpreadsheetWEB through a subdomain (i.e. yourcompany.spreadsheetweb.com) or any other URL.
Federated identity allows users in your network to login to SpreadsheetWeb with their central identity. Users added through this system don’t need to enter their passwords when logging into the control panel. This menu shows the list of federated users added to your SpreadsheetWeb account. Please note that only SystemAdmin users have access to this page.
Adding Federated Users
Click Add Federated User to add a new user.
You can also add users in bulk by importing user details from a data file.
Click Import Selected Users and select your data file in the box provided. Please keep in mind that all imported users will be placed under the selected Group and will have the User Role selected here.
If you need more information about setting up Federation Services on your private server, please contact us.