Setting up Single Sign-On (SSO) with Okta in Spendesk allows for centralized and secure authentication, streamlining workflows for your team. This guide outlines the key steps and requirements for configuring SSO.
Overview
SSO is a feature available with selected Spendesk plans or as a premium add-on. It enables your team to log in using your organization’s centralized identity management system, improving security and user experience.
Prerequisites for Configuration
Before you can set up SSO with Okta, ensure you have the following:
Activated SAML SSO Feature: Contact your Spendesk account manager to enable SAML SSO for your organization. This feature might be dependent on your current plan.
Organization ID (Customer ID): This ID will be provided by your account manager and is required for configuring SSO in Okta.
Step-by-Step Configuration Process
Once you have the necessary prerequisites in place, follow these steps to configure SSO in Okta:
Sign in to Okta Administrator Console: Log in to your Okta Administrator account and navigate to the Applications section.
Create a New Application: Select "Add Application" and choose "SAML 2.0" as the sign-on method. Enter a name for the application (e.g., "Spendesk SSO") and upload logos or icons as needed.
Configure SAML Settings: Provide the Organization ID as the Customer ID in the required fields. Enter the assertion consumer service (ACS) URL and entity ID provided by Spendesk. This ensures seamless communication between Okta and Spendesk.
Customize Attribute Statements (Optional): - Add additional claims if needed, such as email or roles, to match your organization’s authentication policies.
Test Configuration: - Save the configuration and test the application by signing in through Okta. Verify that the SSO redirection works as expected.
Contact Support if Needed: - If any configurations fail or you encounter unexpected issues, reach out to Spendesk Support for assistance.
Troubleshooting Tips
Ensure the Organization ID matches exactly as provided by the Spendesk account manager.
Double-check the ACS URL and entity ID to verify proper setup.
If login attempts fail, consult your Okta admin logs for more insights and adjust settings accordingly.