Thinking of federating with QuickHelp? Need more technical information before you proceed? Check out the most commonly asked questions and answers below.
Question | QuickHelp Response |
---|---|
Which Protocols are supported for SSO? | SAML-p WS-Federation |
Which IdP do you recommend? | QuickHelp is compatible with potentially any Identity Provider that can support WS-Federation or SAML 2.0 standards. |
Support for Single Sign-On (SSO) | IdP-initiated SP-initiated |
Support for Support for Single Log Out (SLO) | None |
Please provide a metadata file. | WS-Federation: https://quickhelp.blob.core.windows.net/metadata/QuickHelpWSFederationMetadata2024.xml SAML 2.0: Metadata is also included in the configuration PDF. |
Supported SSO Bindings | POST Redirect |
Entity/Connection ID | https://auth.quickhelp.com |
Assertion Consumer Service URL | https://auth.quickhelp.com/wsfed https://auth.quickhelp.com/LoginSaml |
Support for self-signed certs | Yes |
Required SAML attributes/Primary Identifier | Email is the only required attribute (must be in attribute assertion). First and Last name, Department, and Title are recommended. |
Default Session Time Out | Users will stay logged in for 48-hours unless they click the "Logout" button – same computer/same browser. This time is configurable in the QuickHelp Admin Portal > Settings. |
Support for deep links | With SSO in place, users will automatically authenticate when using deep links. |
Logout URL | Default Logout URL is https://quickhelp.com/ROUTEURL. A unique Logout URL can be configured in the QuickHelp Admin Portal > Settings. |
Certs v. metadata | QuickHelp requires the IdP metadata, and will extract the certs embedded in the xml file. QuickHelp is configured in such a way, that a customer QuickHelp Admin can configure the SSO portion on the QuickHelp side, so that admin is uploading the metadata to QuickHelp his-/herself. |
Support for signing or encryption of the SAML assertion | We support and require signing. We don’t require encryption. |