Configuring Single Sign-On (SSO)

Create a SAML App in Google

1. Sign in to your Google Admin console using an administrator account.
2. Click Apps > SAML apps.
3. Click the plus icon in the bottom corner.
4. Click on SETUP MY OWN CUSTOM APP.
5. The Google IDP Information window opens and the SSO URL and the Entity ID fields are automatically populated. You need to copy the Entity ID and the SSO field values and download the IDP metadata (Option 2) to paste them into the appropriate fields in Celoxis.
6. After you have entered this information in Celoxis, come back to the admin console and click Next.
7. In the Basic window, enter an Application name and Description.
8. Click Next.
9. In the Service Provider Details window, enter:
   • ACS URL: Enter the value copied from the SSO tab.
   • Entity ID: Enter celoxis.com
   • Start URL: For SaaS, enter https://app.celoxis.com/psa/person.Login.do, for On-Premise, https://your_URL/person.Login.do
10. Leave Signed Response unchecked.
11. Under the Name ID, for Basic Information, select Primary Email.
12. UnderName ID Format drop-down, pick EMAIL.
13. Click on Next.
14. Click Finish.

Enable the SAML App for users

1. Go to Apps > SAML apps.
2. Select the SAML app your created above.
3. At the top of the gray box, click on Settings and choose On for everyone and confirm the settings.

Common Errors

Error: app_not_enabled_for_user
Solution: You have not enabled the SAML app for your users. Follow the steps mentioned above to enable the app for everyone. The same error will be shown if you are logged in to Google account using a different user than the one setup for IDP.

Server Error : No company found with company code: XXXX
Solution: The ACS URL you have entered in Google configuration is incorrect. Copy the correct URL from the ACS URL field under Single Sign-On tab in Celoxis.

Invalid Request, no idpId in request URL or Destination param of the SAML request.
Solution: The IDP URL you entered in Celoxis is incorrect. You need to copy this from your IDP and paste it in Celoxis.

1. Enable My Domain from Setup > Administer > Domain Management > My Domain. Deploy it to all users. This will automatically create Salesforce Identity Provider.
2. Navigate to Administer > Security Controls > Identity Provider. You will see Identity Provider setup details which needs to be entered in Celoxis.
3. C$lick on theDownload Metadata button to download the certificate. The contents of this certificate is to be entered in the IDP Certficate field in Celoxis as described earlier in the document.
4. Now, on the same page below, click on Service Providers are now created via Connected Apps. Click here.
5. On the New Connected App page, enter the following details:
   • Connected App Name
   • Start URL
   • Check the Enable SAML checkbox.
   • Entity ID
   • ACS URL
   • Subject Type: Select Custom Attribute
   • Name ID Format: Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
   • IdP Certificate: Select the appropriate certificate you have entered in Celoxis (Step 3)
6. Click on Save.
7. After the App is created, you now have to associate User profiles to this so that users belonging to these profiles can login via SSO.
   Navigate toManage Apps > Connected Apps. Click on the app your just created.
8. Scroll down and click on Manage Profiles.
9. Select the required profiles and click on Save.

Common Errors

Server Error Not authenticated
Solution: The IDP certificate you have entered in Celoxis is incorrect. Enter the correct certificate you have created for this (Step 3 above) You will face the same error if you have not associated the logging in user's profile with the Connected app as explained in step 7 to 9 above.

1. Log in to your Okta organization as a user with administrative privileges.
2. Click on the Admin button on top-right.
3. Click on the Add Apps label.
4. Click on the Create New App button.
5. In the dialog that opens, select the SAML 2.0 option, then click the Create button.
6. On the General Settings page, enter the application name, for e.g. Celoxis in the App name field, then click the Next button.
7. For Configure SAML step, enter the following details:
   • Single sign on URL: This is the ACS URL you will get from Celoxis
   • Audience URI (SP Entity ID): For SaaS users, enter: https://app.celoxis.com; for On-Premise users, enter the URL of your application.
   • Name ID format: EmailAddress
8. Click Next.
9. In Feedback, select “I’m an Okta customer adding an internal app”, and “This is an internal app that we have created,” then click Finish.
10. In the People section of the application, click on the Assign to People button. Select the required users and click on Done.
11. In the Sign On section of your newly created application click on View Setup Instructions. A new tab opens with the details you need to enter in Celoxis. Fill the Single Sign-On tab in Celoxis as mentioned earlier in this document.

Common Errors

If you are still prompted for credentials after clicking on Connect via SSO and entering SSO credentials, it means that you have entered the ACS URL /Single sign on URL in Okta incorrectly. Please correct and try again.

Sorry, you can't access <app name> because you are not assigned this app in Okta.
The user who is trying to login via SSO is not assigned to the app created in Okta. Redo the step Assign to People mentioned above.

1. Login to your OneLogin account with administrator privileges.
2. Click on Applications > Applications from the main menu.
3. Click the Add App button.
4. Search for SAML Test Connector (IdP w/ attr w/ sign response) and click on it.
5. Enter Celoxis as the Display Name and click on Save.
6. Click on the Configuration tab.
7. Copy the ACL URL from Celoxis to the Recipient and ACS (Consumer) URL tab.
8. In the ACS (Consumer) URL Validator field, escape the ACS URL as mentioned in the OneLogin documentation. In short, you have to prefix the url with ^ put the backslash character (\) before each forward-slash character. e.g. ^https:\/\/app.celoxis.com\/psa\/person.Login.do?code=abc
9. Your OneLogin screen should look something like this: Click the Save button.
10. Click on the SSO tab.
11. Copy the SAML 2.0 Endpoint (HTTP) URL and set it as the IDP URL in Celoxis.

Common Errors

The response was received at <Celoxis URL> instead of <URL>
The ACS (Consumer) URL Validator is not URL escaped as shown in screenshot above.

1. Log in to ADFS Server.
2. Launch the ADFS Management Console.
3. Open the AD FS > Trust Relationships folder from the LHS menu.
4. Right-click on Replying Party Trusts and choose Add Relying Party Trust... menu item.
5. This will open a Wizard. Click on the Start button.
6. In the Select Data Source step, select the Enter data about the relying party manually option. Click Next.
7. In the Specify Display Name step, enter Celoxis. Click Next.
8. In the Choose Profile step, select AD FS profile. Click Next.
9. In the Configure Certificate step, we shall use the defaults. Click Next.
10. In the Configure URL step, check the Enable support for the SAML 2.0 WebSSO protocol option. Under the Relaying party SAML 2.0 SSO service URL, enter the ACS URL copied from Celoxis. Click Next.
11. In the Configure Identifiers step, enter the ACS URL as the Relaying party trust identifier and click Add. Click Next.
12. In the Configure Multi-factor... step, we shall use the defaults. Click Next.
13. In the Choose Issuance Authorization... step, choose Permit all users to access this relying party. Click Next.
14. In the Ready to Add Trust step, you will be shown an overview of your settings. Click Next.
15. In the Finish step, select the Open the Edit Claims... option. Click Close.
16. You should now be shown the Claims Editor window.
17. Click Add Rule... under the Issuance Transform Rules tab.
18. In the Choose Rule Type step, select Send LDAP Attributes as Claims as the Claim Rule Template . Click Next.
19. On the next screen, using Active Directory as your attribute store, do the following:
    • From the LDAP Attribute column, select E-Mail Addresses.
    • From the Outgoing Claim Type, select E-Mail Address.
20. Click OK to save this rule.
21. Click Add Rule... under the Issuance Transform Rules tab to add a new rule.
22. In the Choose Rule Type step, select Transform an Incoming Claim as the Claim Rule Template . Click Next.
23. On the next screen:
    • Select E-Mail Addresses as the Incoming claim type.
    • Select Name ID as the Outgoing claim type.
    • Select EMail as the Outgoing name ID format.
    • Select Pass through all claim values option.
24. Click OK to save this rule.
25. Click OK to finish creating rules.

We shall now export the certificate that needs to be copied over to Celoxis

1. Open the AD FS > Settings > Certficates folder from the LHS menu. The Certificates pane showing all available certificates appears.
2. Select the certificate under Token-Signing in the Certificates pane.
3. Click the Copy to File option in the Details tab of the Certificate window. This starts the Certificate Export wizard.
4. In the Welcome step, click Next.
5. Choose Base64 encoded X.509 (.CER) as the file format in which the certificate is to be exported. Click Next.
6. Save the file to an appropriate location and complete the wizard.
7. Ensure that the saved file has the .CER extension.
8. You will need to copy paste the contents of this file in the IDP Certficate field in Celoxis as described earlier in this document.

1. Log in to the Azure portal.
2. In the LHS menu, click Azure Active Directory.
3. In the Azure Active Directory menu click Enterprise applications.
4. Click New application at the top of the screen.
5. In the Add an application section, choose Non-gallery application.
6. Give the new application a name (e.g. Celoxis SSO) and then click Add at the bottom of the screen. This will add a custom application to your Azure Active Directory. Note: If you do not have Azure AD Premium activated, you will not be able to enter the name of the application.
7. On the application page, click Users and groups in the LHS menu.
8. At the top page the right pane, click Add user to assign users or groups to this application.
9. Click Single sign-on in the LHS menu and then choose SAML as the single sign-on method.
10. Click on the icon next to the title of the Basic SAML Configuration panel and enter details as follows:
    • Identifier (Entity ID): Enter the value from the Single Sign-On tab (refer the image included above).
    • Reply URL (Assertion Consumer Service URL): Copy the details from under the ACS URL field (Admin > Company Settings)
    • Sign on URL: For SaaS enter https://app.celoxis.com. For On-Premise enter your URL.
    • Relay State: Skip this field
    • Logout URL: For SaaS enter https://app.celoxis.com/psa/logout.do. For On-Premise enter [your-url]/psa/logout.do
11. Return to the setup screen.
12. Click on the icon next to the title of the User Attributes & Claims panel.
13. Click on the icon next to Name identifier value. A Manage user claims sidebar will appear.
14. Enter a name and select user.mail in the Source attribute drop-down. Click Save.
15. Return to the setup screen.
16. Click on the icon next to the title of the SAML Signing Certificate panel.
17. Enter a notification email for the certificate expiry reminders. Click Save.
18. Return to the setup screen.
19. Click on Download next to the Certificate (Base64) option to save the certificate file on your computer. You should copy paste this in Celoxis as described earlier in this document.
20. Return to the setup screen.
21. Click on Validate to validate single sign-on with Celoxis.