SAML, or Security Assertion Markup Language, enables you to access multiple web applications using one set of login credentials. You do not need to remember multiple usernames and passwords. It increases the security of your platform by avoiding the need to store passwords.
By the use of SAML, LeadAngel can communicate with other applications and can pass authentication information in a particular format.
Steps to create SAML
1. Create SAML App
The first step is to create a custom SAML App in OKTA for LeadAngel.
2. Customize SAML App
Next is to configure the App
- App name: Specify a name (Such as LeadAngel, LeadAngel Sandbox etc)
- App logo: Add a logo to accompany your integration in the Okta org.
- App visibility: Choose whether to hide your integration from your end users' homepage.
3. Configure SAML App
A SAML 2.0 configuration requires a combination of information from your org (i.e. OKTA) and the LeadAngel app.
4. SAML Integration Feedback
5. Copy SAML Configuration from OKTA
Copy the following to configure the LeadAngel application
-
Identity Provider Single Sign-On URL
-
Identity Provider Issuer
-
Certificate file
6. Configure LeadAngel Application
1. Sign in to app.leadangel.com
2. Go to Administration > Integration > SAML configuration
Configure following
- SAML Provider Entity ID: Identity Provider Issuer copied from OKTA. Entity ID is a globally unique name for an Identity Provider or a Service Provider. It is how other services identify your entity.
- Single Sign On URL: Identity Provider Single Sign On URL copied from OKTA. It is the endpoint that is dedicated to handling SAML transactions. This value defines the URL you will be redirected to when logging in.
- Logout URL: https://app.leadangel.com/uiapi/sso/logout. It allows you to terminate all server sessions established via SAML SSO by initiating the logout process once.
- Insert Certificate copied from OKTA. Remove the lines containing “----- BEGIN CERTIFICATE —-” and “----- END CERTIFICATE —--”. It is used to sign SAML requests, responses, and assertions from the service to relying on applications such as WebEx or Google Apps.
2. Select the appropriate production, sandbox vs test instance (already set up in OKTA)
It might take up to 5 min for the certificate and signature to propagate.
7. Finally, click on Update.