Thinking of federating with QuickHelp? Need more technical information before you proceed? Check out the most commonly asked questions and answers below.
|Which Protocols are supported for SSO?||SAML-p|
|Support for Single Sign-On (SSO)||IdP-initiated |
|Support for Support for Single Log Out (SLO)||None|
|Please provide a metadata file.||WS-Federation:|
Metadata is also included in the configuration PDF.
|Supported SSO Bindings||POST|
|Assertion Consumer Service URL||https://auth.quickhelp.com/wsfed|
|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.|