Set Up Single Sign On
SecureSheet allows organizations to sign into the application through Single Sign On. Follow these set-up instructions.
SecureSheet only supports an IDP Initiated SAML login request for bypassing our login page.
- As a Service Provider (SP), here is SecureSheet's SSO information:
- SecureSheet Service Provider entityID = "https://www.securesheet-cloud.com/sso"
- Assertion Consumer Service (ACS) URL = "https://www.securesheet-cloud.com/sso/SAML/login.aspx"
- Here is what SecureSheet needs from you as an Identity Provider (IP):
- Your Identity Provider entityID.
- SecureSheet requests that the Email Address of the user be passed as name identifier (the Subject’s "NameID" element). The SecureSheet system shares SecureSheets with end users by email address so it needs this parameter for automatic sign on, which will in turn establish the appropriate security access within SecureSheet for the authenticated user.
- Your Authentication Certificate (or SecureSheet can pull it from your "X509Certificate" tag).
- Click here for the SecureSheet metadata file.
- When you have completed your setup, send an export of your Federation Metadata XML file to SecureSheet Support.
Once set up is complete on the SecureSheet side, you can test SSO login through your Identity Provider (IP) initiated link. You will see a user login test somewhere in your SSO administrative tools. SecureSheet support staff never see this link nor have access to it. This is the link you will need to share with your end users so they can access SecureSheet through your SSO set up.
- For an example of an OKTA set up, click here.
- For an example of an AZURE set up, click here.
- For an example of an ADFS set up, click here.
NOTE: If you would like to include a SecureSheet logo on an internal portal page, click here for a square SecureSheet logo file.
NOTE: If your Authentication Certificate expires, send your updated metadata file to SecureSheet Support and we will update your certification information in our SSO setup for your organization. The transition should be seamless to end users and it can be coordinated in detail as needed with SecureSheet Support.