Setting up an Enterprise OIDC login
Enterprise SSO using OpenID Connect (OIDC) allows organizations to centralize authentication and access control, improving security while simplifying user management across systems.
Enterprise SSO setup is a collaborative process that typically involves your internal IT or Identity team and Allspice. While Allspice supports standard OIDC providers, the exact configuration depends on how your organization manages identity and access, so early coordination is important.
Because of this, we strongly recommend identifying the appropriate IT contact during your evaluation period and looping them and Allspice into the process as soon as possible.
What we’ll need to get started
To begin configuring Enterprise SSO, your IT team will need to provide the following:
- Confirmation of which identity provider you are using (for example, Okta or Azure Active Directory)
- The Client ID for the OIDC application
- The Client Secret associated with that application
- The Metadata URL (OIDC discovery endpoint)
- How Group Mapping is defined between your identity provider and teams in Allspice
Once this information is available, Allspice can help guide the remaining configuration and testing.
Why involving IT early matters
Enterprise SSO often involves authentication and security considerations that require input from your IT team. Bringing them into the conversation early can help streamline setup.