# Single-Sign-On CrowdComms currently supports SSO via the SAML2 standard. This is an enterprise-grade industry standard to allow users to authenticate between Identity Providers (IDPs) and Service Providers (SPs). The CrowdComms platform is a Service Provider and examples of IDPs include Microsoft Active Directory, OneLogin, Okta and others. # New Page # FREQUENTLY ASKED QUESTIONS **Q:** Do all the delegates still need to be registered on the site as usual? **A:** No if they’re logging in via their company’s directory. With SSO, the user’s basic information such as First name, Last name, Email, and Phone number will be auto-populated in the event app. **Q:** My event will consist of delegates from my own company and speakers from outside the company, can I still use SSO? **A:** Yes, delegates from within the company who has been authenticated will be able to utilise the SSO function. The speakers from outside the company will be able to log in to the event app using their username and password. **Q:** Not everyone in my company’s Active Directory will be invited to my company’s event, can I still use SSO and tailor only the relevant people to have access to the event app? **A:** Yes, once your business IT contact has set up the SAML2, you can work with them to decide who from your company should get delegate access to the event app. # INTRODUCTION #### **SINGLE SIGN-ON (SSO)** Single sign-on (SSO) is an authentication process that allows a user to use one set of login credentials, for example, a username and password, to access multiple applications. #### **PURPOSE** SSO helps clients and their users with the challenge of maintaining the different credentials for different applications separately which streamlines the process of signing on without the need to re-enter the password. With SSO end-users time and efforts get minimized as they don’t need to constantly sign in and out separately into multiple applications. #### **PROCESS** Setting up SSO must be done by the client's IT department or technical personal. The setup will involve authenticating the Identity Prover (IDP) i.e., the client with the Service Provider (SP) i.e., Crowdcomms event platform. [![image-1630410205581.png](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2021-08/scaled-1680-/image-1630410205581.png)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2021-08/image-1630410205581.png) # SAML2 How **does SSO work**? **SSO works** based upon a trust relationship set up between an application, known as the service provider, and an identity provider, like OneLogin. ... In **SSO**, this identity data takes the form of tokens that contain identifying bits of information about the user like a user's email address or a username. ## **How to set up saml2-compatible identity providers** ### ***Manual Set Up*** - Log into CMS - Select App - Click on "Settings" - Click on "Authentication" and then "Single Sign On" - Click on "Add Provider" - Check the "Manual Set Up" option - Fill in; "Provider Name" - Copy the "Issuer URL" into the "SAML Entity I.D" in CMS - Copy the "SAML2 Endpoint" into the "SSO Login URL" field in CMS - Copy the "Certificate" into the required field in CMS - Fill in the "Unique ID" field in CMS under field mapping - Click "Save changes" in CMS [![SSO 4.png](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/scaled-1680-/sso-4.png)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/sso-4.png) ### ***Import IDP Metadata XML*** Required details: - Entity ID: https://saml.crowdcomms.com - Reply URL: [https://api.crowdcomms.com/complete/saml/](https://api.crowdcomms.com/complete/saml/) Note: this needs to be summit-api for apps using the Summit enviroment, and dlt-api for apps using the Deloitte environment. Deloitte apps using the main environment should still use just api. Using the above you should be able to import your metadata with the following steps: - Fill in; "Provider Name" - Return to IDP and copy the Metadata URL - Copy the link into the CMS field "Metadata URL" - Insert a name into the "Unique User I.D" field (for example; NameId) - this is based on the field mapping the client sets up. They will map their Active Directory fields to potentially something shorter, eg their ID field could be mapped to 'uniqueid', and so instead of filling in NameId here, you'd fill in uniqueid - Click Save in CMS - Copy the "Relay State URL" into the Configuration TAB - Copy the "Audience" into the Configuration TAB - Copy the "Recipient" into the Configuration TAB [![SSO.png](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/scaled-1680-/sso.png)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/sso.png) ### ***Branding the Login Page with SSO*** The Front End Login page can be branded with unique text and/or with a logo in the "Display Options" section of the "Edit Auth Provider" page [![SSO 3.png](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/scaled-1680-/sso-3.png)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/sso-3.png) - Upload the image you wish to add to the login page - Type the text you would like to appear (For Example... "Please log in") - Click Save ### ***Field Mapping*** - Click on "Edit Provider" to edit the SSO you set up in the previous step - Scroll down and click on "Add Mapping" [![SSO 2.png](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/scaled-1680-/sso-2.png)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2024-02/sso-2.png) - Enter each field mapping and click "Save". Again these are based on the field mappings the client sets up. We take the output of their mapping, and map it to a profile field in our own system - Click Save ### ***Logging into Front End*** - Open up Front End of App [![FE-SSO-Login-Screen.PNG](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2021-05/scaled-1680-/FE-SSO-Login-Screen.PNG)](https://crowdcomms-docs-media.s3.amazonaws.com/uploads/images/gallery/2021-05/FE-SSO-Login-Screen.PNG) - Click on "Sign In" - Enter your credentials - At this point, if any more User information is required then a screen will appear for the user to fill them in (for example; first name), otherwise, you will receive a "Success Screen" before FE loads up - As this is the first time the User will of logged in, they will receive the company privacy message to accept or decline - The user is now logged into the App