Single Sign On (SSO) for Multi-Tenant Deployments
Introduction
Appspace 5.2 introduces our single sign on (SSO) integration feature for on-premise deployments. With SSO, Appspace allows users to seamlessly and securely connect to Appspace using a single set of credentials, simplifying username and password management.
This guide is based on ADFS being the Identity Provider and Appspace being the Service Provider. As this will be a complicated configuration/installation guide, we’ll break it down into smaller sections:
Section 4: Enabling and Configuring SSO
Section 1: Requirements
Active Directory Server
- Windows Server 2008 R2
- SSL configured
- Windows Server Administrator credentials
Active Directory Federation Services (ADFS)
- Can be installed on the Active Directory Server
- Version 2.0 for Windows Server 2008 R2
- SSL configured
- Windows Server Administrator credentials
Network
- All servers must belong to the same domain or sub domain
Appspace Server
- Version 5.2 and above
- SSL configured
- Windows Server Administrator credentials
- Appspace Portal Administrator, Account Administrator or Account Owner role
- All users created on the Appspace server needs to have an email (can be used as the login as well)
Section 2: How SSO Works
A user starts by trying to log into Appspace. Upon accessing the login page, the user will be redirected to an SSO login page. The user will then have to authenticate his/her login credentials against the Identity Provider. Upon successful authentication, the Identity Provider will send a SAML assertion to Appspace via the web browser to allow the user to log into Appspace.
Section 3: Installing ADFS
Note
This can be performed on the AD server or on a separate server.
Start by downloading Active Directory Federation Services 2.0. To do so, navigate to http://www.microsoft.com/en-in/download/details.aspx?id=10909 and click Continue.
Choose the version based on your Windows Server version and click Next to start the download.
Note
RTW/W2K8R2/amd64/AdfsSetup.exe – This is for Windows Server 2008 R2 SP1
RTW/W2K8/amd64/AdfsSetup.exe – This is for Windows Server 2008 R1 SP2 64bit
RTW/W2K8/x86/AdfsSetup.exe – This is for Windows Server R1 SP2 32bit
Once the download is complete, locate the .exe file and double click it.
Click Run.
Click Next.
Check the checkbox to agree to the EULA followed by the Next button.
Select the Federation server option and click Next.
Click Next.
Select the option to start the ADFS 2.0 Management snap-in when this wizard closes and click Finish.
On the AD FS Server configuration wizard select the Create a new Federation Service option and click Next.
Select the Stand-alone federation server option.
The wizard will automatically detect your SSL certificate. The details of the SSL certificate and the Federation Service name will be populated automatically if your SSL certificate is valid. Click Next to proceed.
Click Next.
Wait for the configuration to finish and click Close.
Section 4: Enabling and Configuring SSO
To begin, we will need to download the Identity Provider (ADFS) metadata. Open a browser and key in the URL https://<ADFS FQDN or IP>/FederationMetadata/2007-06/FederationMetadata.xmlto download the metadata.
Note
This metadata is used by the Identity Provider (ADFS) to recognise the Service Provider (Appspace). This process involves downloading the metadata in xml format, uploading to and re-downloading from Appspace and finally re-uploading it to the Identity Provider (ADFS).
Log into your Appspace instance and click on the user button followed by System.
Note
You’ll have to be a Portal Administrator to access system settings.
Click Authentication.
Select Multiple Tenancy.
Click Save.
Click Yes.
Click the Click Here link.
Fill in your Windows server administrator credentials and click Apply.
Click Yes.
Allow some time for the Appspace to restart.
For each tenanted account, click the Profile button and select Account.
Reminder
This has to be done for each account.
Click the SSO tab.
You will be given three SSO authentication options: OFF, Optional or Required. We’ll be selecting Optional in this example.
Note
Optional – Users can select between using their Appspace login credentials or via SSO (AD credentials)
Required – Users can only login via SSO (AD credentials)
You will be given two SSO binding options; Redirect or POST. We’ll be using POST in this example.
Note
Redirect – Users will be redirected to the Identity Provider. SSO details will be passed in a query string with “?SAMLRequest=……” as part of the URL
Post – SSO details will not be passed through a query string but will be passed using the POST method. For this method to work, you must ensure that the Identity Provider has direct access to the Appspace Server.
You will be given two Identity Provider (IdP) configuration methods; Use IdP Metadata or Manual. We’ll be using Use IdP Metadata in this example.
Upon selecting the Use IdP Metadata option, you’ll need to upload the metadata xml file downloaded in Step 1. Click browse and locate that file. Click Open to upload the metadata file to the Appspace server.
The upload path will be displayed. You can now skip to Step 23`_.
To use the Manual configuration method, you will need to fill in the SSO URL as well as the X.509 certificate.
Fill in the URL of the ADFS server with https://<ADFS server’s FQDN/IP>/adfs/ls/
To fill in the X.509 certificate, locate the downloaded FederatedMetadata.xml in Step 1 and open it in a browser.
Locate the line <X509Certificate> and copy its associated text.
Paste the text in the X509 Certificate textbox.
You will finally be given the option to enable or disable Metadata Signing. Click Change to show the options. We’ll be disabling this feature in this example.
Note
Enabled – The SP metadata file will be generated in an ‘Encrypted’ format
Disabled – The SP metadata file will be generated in a ‘Plain text’ format
Click Save.
Click Download to download the Service Provider’s metadata file. Transfer the file to your Identity Provider (ADFS).
Section 5: Configuring ADFS Relying Party Trust
Note
This section is performed on the Identity Provider (ADFS) server.
On the ADFS server launch AD FS 2.0 Management.
Expand the Trust Relationship folder and select the Relying Party Trusts folder. To add a Relying Party trust click Add Relying Party Trust under the Actions pane.
Click the Start button.
Select the “Import data about the relying party from a file” option and click Browse.
Locate and select the metadata file that was downloaded from the Appspace server and click Next.
Give the Relying Party trust a name and click Next.
Select the “Permit all users to access this relying party” option and click Next.
Click Next.
Ensure that the checkbox for “Open the Edit Claim Rules dialog for this relying party trust when the wizard closes” is ticked.
On the Edit Claim Rule window, click Add Rule.
Select the “Send LDAP Attributes as Claims” option and click Next.
Name the Claim Rule and select Active Directory as the attribute store. Refer to the screenshot below for the Mapping of LDAP attributes to outgoing types value. Click Finish when done.
Note
This step mandates that all Appspace users (authenticating via SSO) are required to have email addresses (can be used as the usernames as well).
Click Add Rule and select “Transform an Incoming Claim” followed by the Next button.
#. Name the Claim rule and configure the rest of the fields as what is shown on the screenshot below. Click Finish when done.
Click Apply.
Click OK.
Click Relying Party Trusts and select your display name.
Click Advanced and select SHA-1 as the secure hash algorithm. Click Apply when done.
Section 6: Logging in with SSO
Login with your username. (This should be an email). You will be redirected to the SSO login page provided by your Identity Provider.
Warning
You must use HTTPS for SSO to work.
Enter your credentials. Upon successful authentication, you will be redirected back to your Appspace Dashboard.
