eQuest admin supports SAML single sign-on, started from your identity provider (IdP). The sign-in request with the SAML assertion has to come from your server, so just clicking an eQuest SAML link won't sign you in.
Why use SSO
No typing credentials, no passwords to remember or renew, and no weak passwords.
Set up your identity provider
- Create an x509 key pair.
- Create a SAML link with these settings:
- SAML Version: 2.0
- Message Signing: Assertion only
- Signature Method: SHA256
- Name Identifier: Email address
- x509 key pair: the one you just created
- Assertion URL and Service Provider Metadata URL: from eQuest admin (next step)
Get the eQuest URLs
In eQuest admin, go to Advanced Settings > SAML SSO Configuration to find the Entity ID, Assertion URL and Metadata URL.
Turn on SSO in eQuest
- Check Enable SSO.
- In the Fingerprint field, click From cert...
- Paste your public certificate, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.
- Click Get Key. When you save, the certificate is converted into your fingerprint.
Admin accounts
Each person who needs admin access needs their own eQuest admin account. The email address is what links them, so make sure each admin account's Account Email matches the email your IdP sends.
Test it
Once everything's set up, you should be able to sign in to eQuest admin from the SAML link in your application.
Testing vs production: the Assertion and Metadata URLs are different in eQuest's test environment, so get them from the environment you're setting up.