Single Sign On
Stackla supports Secure Assertion Markup Language (SAML), which allows you to provide single sign-on (SSO) for your Stackla account using enterprise identity providers such as Active Directory and LDAP.
By using SAML, a user is automatically verified with the identity provider when they sign in. The user can then access the Stackla Platform without being prompted to enter separate login credentials.
Key benefits of Stackla’s SSO offering include:
- Clients are able to enforce their respective password standards
- Access to Stackla is routed through the client’s Identity Provider (IdP)
- Clients are able to revoke access to any system, including Stackla, by locking the account and/or changing the password
- Clients can implement their own Two-Factor Authentication (2FA) or Multi-Factor Authentication (MFA) standards
- End Users are able to leverage the same credentials they use for other systems
- Clients are able to implement their own polices around Password resets
- Staff are discouraged from sharing their accounts
- Protocol: SAML 2.0
- Relying Party Name: Stackla
- Supported SAML Profiles: IdP Initiated SSO
- Claim Type: NameIDPolicy: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
- Hash Algorithm: SHA-256
- Supported SAML Profiles: SP-Initiated SSO
- Issuance Authorization Rules: Permit All Users
Stackla’s Single Sign On (SSO) offering is designed to work with organisations own Identity Provider services, such as Active Directory and LDAP, as well as online SAML services, such as Okta, Google and SalesForce.
Setup guides for the service are available below.
- Getting started with Single Sign On
- How to configure SAML 2.0 for Stackla on Okta
- Setup Stackla as a Google SAML App
- Setup Stackla as a SalesForce Connected App