SAML how-to guides
These guides give provider-specific setup instructions for SAML 2.0 single sign-on with AxonOps Cloud. Every integration follows the same shape: create and configure an application in the identity provider, define the AxonOps roles the identity provider will send, and complete the configuration in the AxonOps console. The AxonOps-side configuration is the same for every provider; only the identity-provider-side steps differ.
Before starting any guide, confirm the prerequisites listed on the SAML overview are in place.
Provider interfaces change
The guides are worked examples, correct at the time of writing. Identity providers revise their consoles and menus over time, so individual screenshots and steps may no longer match the current product; where they differ, the provider's own documentation is the authoritative reference. The AxonOps-side values (the Reply URL, Entity ID, and role strings) are unaffected and remain as described in the SAML overview.
Microsoft Entra ID
Section titled “Microsoft Entra ID”Configuring Microsoft Entra ID as the identity provider is a three-part guide:
- 1. Create the Entra ID application: register a non-gallery enterprise application and set the Entity ID and Reply URL.
- 2. Configure app roles for AxonOps: create app roles carrying AxonOps role values and assign users and groups.
- 3. Configure SAML in the AxonOps console: upload the federation metadata, set the Entity ID and SP certificate, and verify sign-in.
Other supported identity providers
Section titled “Other supported identity providers”AxonOps Cloud also supports Okta and JumpCloud as SAML identity providers. The AxonOps-side configuration is identical for every provider and is covered in part 3 of the Microsoft Entra ID guide.