Managing SSO Configurations
Theme: Configure
Who Is It For? System Administrator, Automation Engineer
What Is It?
Use this procedure to manage SSO Configurations in Solution Manager.
Administration
Required Privileges
To configure the Single Sign-On setting, you must have one of the following:
- Role: Role_ocadm
- Function Privilege: Maintain Server Options
Configuring SSO
To configure SSO Settings, go to Library > Server Options > Select the SSO tab.
SSO Configuration Fields
-
Select the Switch to enable the SSO login button
-
Enter a Provider. Select the identity provider (IdP) from the Provider list. Options include Okta, Azure AD, Google, and Other
-
Enter an Authority. The URL of the OIDC/OAuth2 provider
-
Enter a Client ID. Your client application's identifier as registered with the OIDC/OAuth2 provider
-
Enter a Redirect URI. The location where the authorization server sends the user after successful authorization. Adding /login/callback is required for SSO to function. For example,
https://host:8443/login/callback. -
Enter a Scope. The scopes requested from the OIDC/OAuth2 provider (blank by default). Separate multiple scopes with a space
* OpenID Connect (OIDC) is an open authentication protocol that works on top of the OAuth 2.0 (OAuth2) framework.
Google-Only Fields
Selecting Google as the Provider adds two additional required fields, shown only for that provider:
-
Enter one or more Permitted Workspace Domains. Each entry is a Google Workspace domain (for example,
acme.com); press Enter after typing a domain to add it as a chip. Only Google accounts belonging to one of these domains can sign in — this is the only setting that stops any Google account, including a personal Gmail account, from signing in. Domains are not case-sensitive and duplicates are ignored -
Enter a Client Secret. The client secret from your Google OAuth client. This value is never displayed again once saved — leaving the field blank on a later save keeps the previously stored secret
Google requires the https://www.googleapis.com/auth/cloud-identity.groups.readonly scope, in addition to openid and email, so OpCon can look up the groups a signed-in user belongs to. Enter all three scopes, space-separated, in the Scope field, for example: openid email https://www.googleapis.com/auth/cloud-identity.groups.readonly
Test Connection Button
The test connection button retrieves metadata from the IdP using the value in the Authority field. The Authority field is required to establish a proper configuration with the IdP and enable communication with the OpenID Connect application.
Group Mappings
-
Enter a Group Name matching the group name used in your IdP
-
Enter a Role representing a valid OpCon role
-
Select Save
- If the switch is On, values are required in all fields, including Group Mappings
- SSO can be implemented with any IdP that follows the OpenID Connect authentication protocol
- The IdP must return a token with a groups claim containing the user's group memberships and an opconid claim composed of the user's email
- For Google, group names are matched to Group Mappings without regard to letter case, since Google Workspace always returns group email addresses in lowercase. For every other provider, group names must match exactly
- For Google, OpCon reads only the groups the user belongs to directly. Membership that comes through a group nested inside another group is not included
- See examples below for Okta, Azure AD, and Google Workspace
Once a user accesses Solution Manager through SSO, their password automatically changes to a random value, ensuring SSO is the only means of authentication.
The following table describes actions taken when a user logs in through Single Sign-On.
| Exists in IdP Group | Exists in OpCon | Member of OpCon Role | Can access application in IdP | Enabled in OpCon | Action Taken |
|---|---|---|---|---|---|
| Y | Y | Y | Y | Y | No action user is already in sync |
| Y | N | N/A | Y | N/A | User created and added to role |
| Y | Y | N | Y | Y | User added to role |
| Y | Y | Y | Y | N | User refused. The account is disabled in OpCon and stays disabled |
| Y | Y | Y | N | Y | No action since user cannot access the application |
| Y | Y | Y | N | N | No action since user cannot access the application |
| N | Y | Y | N/A | Y | No action since user does not belong to an existing group |
| N | Y | Y | N/A | N | No action since user does not belong to an existing group |
| N | N | N/A | N/A | N/A | No action |
- Group name values should be unique
- Group names can be linked to many roles
- Roles can be linked to many group names
Creating Applications That Are OpenID Connect Compatible
Okta Application
These steps create a custom Okta application that returns custom optional claims in an access token used by SMAOpConRestApi. The user performing these steps must have privileges to create an application, assign users, and create custom claims.
- Log in to Okta and select Admin in the upper right corner to go to the administration dashboard

- From the administration dashboard, select Applications in the left navigation

- Select the Create App Integration button
- In the modal, select:
- Sign-in method: OIDC - OpenID Connect
- Application type: Single-Page Application

- Select Next
- Set the following options:
- Grant type: Authorization Code
- Sign-in redirect URI:
https://<hostname:443>/login/callback— must include /login/callback; this value maps to the Redirect URI in the SSO configuration tab - Sign-out redirect URI: not required
- Controlled access: set based on your organization's needs

- Select Save
- Note the Customer ID value — it is used to configure SSO in Solution Manager
- In the modal, select:
- Open the newly created application and go to Assignments. Assign the relevant users from your organization

- Go to Security > API from the main menu
- On the Authorization Server tab, select the default server. Note the Issuer URI — this is the Authority value for SSO configuration
- Select the Claims tab

- Select Add Claim and configure a groups claim:
- Token type: Access Token
- Regex:
.* - Name: groups

- Repeat to add an opconid claim with appuser.email in the Value field

- Select the Settings tab and note the Issuer — used as the Authority value

- Select the Token Preview tab:
- Enter your application name
- Select Authorization Code for Grant Type
- Select a user with access to this application
- Enter openid in the Scopes field
- Select Preview Token, then select the token tab. Confirm groups and opconid claims appear

- Select the Access Policies tab
- Select Edit on the Default Policy Rule row. Confirm Authorization Code is selected

- Select Edit on the Default Policy Rule row. Confirm Authorization Code is selected
- Enter openid in the Scope field in the SSO configuration tab in Solution Manager
- The user's email must match their username and will be used to pair with or create an OpCon user
Azure AD Application
These steps create a custom Azure AD application that grants SMAOpConRestApi access to Microsoft Graph API. The user performing these steps must have privileges to create an application, assign users, and assign Microsoft Graph API permissions.
-
Go to Azure Active Directory > App registrations
- Select New registration and configure:
- Add a name
- Select who can access (for example, Single tenant)
- Select Single-page application (SPA)
- Set the Redirect URI (for example,
https://<yourhostname>:8080/login/callback) — must include /login/callback
- Select Register
- Select New registration and configure:
-
Open the newly created application (Home > Azure Active Directory > App registrations > your application)
-
Go to Authentication in the side menu. Confirm a redirect value is present in the single-page application area

-
Go to Overview in the left navigation. Note:
- The application (customer) ID — used as Customer ID in Solution Manager
- Select Endpoints, copy the OpenID Connect value, paste it in a browser, and find the issuer value in the JSON — used as Authority in Solution Manager

-
Go to API permissions in the left navigation
- Select Add a permission > Microsoft Graph

- Select Delegated permissions, search groupmember, and select GroupMember.Read.All

- Search user.read and select User.Read
- Select Add permissions, then select Grant admin consent

- Select Add a permission > Microsoft Graph
-
Go to Manifest in the left navigation. Set accessTokenAcceptedVersion to 2

-
Restrict access to the application (optional)
- Go to Azure Active Directory > Enterprise Applications > All applications and select your application
- Select Properties, set Assignment Required to Yes, and save

- Under Manage, select Users and groups > Add user/group. Assign the users and groups that need access. Confirm they appear in the updated list
- Add openid in the Scope field in the SSO configuration tab in Solution Manager
- The token from this application is used to call Microsoft Graph API:
https://graph.microsoft.com/v1.0/me— retrieves userPrincipalName (user's email), used as the OpCon identifierhttps://graph.microsoft.com/v1.0/me/getMemberGroups— retrieves group IDs the user belongs tohttps://graph.microsoft.com/v1.0/groups/{group-guid}— retrieves displayName, mapped against an existing group
Google Workspace Application
These steps create a Google Cloud OAuth client that grants SMAOpConRestApi access to a Google Workspace user's identity and group memberships. The user performing these steps must be able to create a Google Cloud project and, separately, must ask a Google Workspace administrator to enable an API and add users and groups.
-
Sign in to the Google Cloud console and create a new project (or select an existing one)
-
Go to APIs & Services > Library, search for Cloud Identity API, and select Enable
cautionSkipping this step causes group lookups to fail with a permission error after a user otherwise signs in successfully
-
Go to Google Auth Platform (formerly named "OAuth consent screen")
-
On the Audience tab, set the user type to Internal (recommended, restricts sign-in to your Workspace domain) or External
-
On the Data Access tab, select Add or remove scopes, add the three required scopes — openid,
.../auth/userinfo.email, and.../auth/cloud-identity.groups.readonly(search "Cloud Identity API" to find it; do not select the similarly namedcloud-identity.devices.lookupscope) — then select Update followed by Save
-
-
On the Clients tab, select Create Client
-
Set Application type to Web application
-
Under Authorized redirect URIs, add your Solution Manager redirect URI — must include /login/callback, for example
https://<yourhostname>/login/callback
-
Select Save. Note the Client ID and Client Secret shown — used in the SSO configuration tab. The Client Secret is only shown once and cannot be viewed again; if it is lost, add a new secret to the same client rather than recreating it
-
-
In the Google Admin console, ask your Workspace administrator to:
- Create or identify the groups to map to OpCon roles, and add the relevant users to each group
- Confirm each group's Who can view members setting includes group members — OpCon's group lookup runs as the signed-in user, so a user who cannot see their own group memberships in
groups.google.comcannot sign in to OpCon either
- Enter openid email
https://www.googleapis.com/auth/cloud-identity.groups.readonlyin the Scope field in the SSO configuration tab in Solution Manager - Enter
https://accounts.google.comin the Authority field. Unlike Okta or Azure AD, this value is the same for every Google Workspace domain — it is not specific to your organization - The user's Google email address is used as the OpCon identifier
- The token exchange happens on the OpCon server, not in the browser — this is why a Client Secret field exists for Google but not for Okta or Azure AD
Common errors when connecting to your IdP OIDC application:
- Invalid Redirect URI: The redirect URI in the SSO configuration must match the one configured in your IdP. Mismatches prevent successful authentication
- Incorrect Authority: The authority (OIDC provider URL) must match exactly. Any mismatch causes connection and authentication failures
- Invalid Customer ID: The customer ID in the SSO configuration must match the one expected by your IdP. An incorrect customer ID prevents successful authentication
- Google: "have not been mapped to any roles": The signed-in Google account belongs to no group listed in Group Mappings. Add the group, or add the user to a mapped group in Google Admin
- Google: "User's Workspace domain '...' does not match the configured permitted domain" or "User account does not belong to a Google Workspace domain": These appear after the Google sign-in completes. The account's domain is not in Permitted Workspace Domains, or the account is a personal Gmail account rather than a Workspace account
Security Considerations
Authentication
SSO in OpCon uses OpenID Connect (OIDC), which operates on top of the OAuth 2.0 framework. Supported identity providers include Okta, Azure AD, Google Workspace, and any IdP that follows the OIDC authentication protocol. The IdP must return a token with a groups claim containing the user's group memberships and an opconid claim containing the user's email.
Once a user accesses Solution Manager through SSO, their OpCon password is automatically changed to a random value, ensuring SSO becomes the only means of authentication for that account.
The Redirect URI in the SSO configuration must include /login/callback and must exactly match the redirect URI configured in the IdP. Mismatches in the Redirect URI, Authority URL, or Client ID prevent successful authentication.
For Okta, the Authorization Code grant type is used with the openid scope. For Azure AD, the application requires Delegated permissions for GroupMember.Read.All and User.Read from Microsoft Graph API, and admin consent must be granted. For Google, the browser performs the sign-in and hands an authorization code to the OpCon server, which exchanges it for the user's identity and group memberships directly with Google — the Client Secret is required for this exchange and never leaves the server.
Authorization
Configuring SSO requires the Role_ocadm role or the Maintain Server Options function privilege. Group Mappings link IdP group names to OpCon roles. When a user logs in via SSO, OpCon automatically creates the user account if it does not exist and adds it to the mapped role. Users removed from an IdP group are not automatically disabled in OpCon.
For Google, a signed-in user's account must belong to a domain listed in Permitted Workspace Domains. A Google account outside every listed domain — including a personal Gmail account — is refused before OpCon checks group membership.
Sensitive Data
The Client ID, Authority URL, and Redirect URI are registered with the IdP and must match the values configured in Solution Manager. For Okta, the Customer ID from the app registration is a sensitive identifier. For Azure AD, the Application ID, Tenant ID, and access token version (set to 2 in the manifest) are required for the integration. For Google, the Client Secret is stored encrypted and is never displayed again after it is saved; the SSO configuration screen only shows whether a secret is currently stored.
Configuration Options
| Setting | What It Does | Default | Notes |
|---|---|---|---|
| Provider | Identity provider (IdP) used for SSO | — | Options: Okta, Azure AD, Google, Other |
| Authority | URL of the OIDC/OAuth2 provider | — | Required; the Test Connection button uses this value to retrieve IdP metadata |
| Client ID | Client application identifier registered with the OIDC/OAuth2 provider | — | — |
| Redirect URI | Location the authorization server sends the user after successful authorization | — | Must include /login/callback |
| Scope | Scopes requested from the OIDC/OAuth2 provider | — | Separate multiple scopes with a space. For Google, must also include email and https://www.googleapis.com/auth/cloud-identity.groups.readonly |
| Permitted Workspace Domains | Google Workspace domains allowed to sign in | — | Google only; required when Provider is Google |
| Client Secret | Client secret from the OAuth client | — | Google only; required when Provider is Google. Write-only — never displayed after saving |
FAQs
Q: Which identity providers does OpCon SSO support?
OpCon SSO uses OpenID Connect (OIDC) on top of the OAuth 2.0 framework. It supports Okta, Azure AD, Google Workspace, and any identity provider that follows the OIDC authentication protocol.
Q: Why does Google need a Client Secret when Okta and Azure AD don't?
Google requires a client secret to exchange a sign-in code for a user's identity, even when the sign-in itself uses PKCE (a security measure that protects the sign-in code). OpCon performs that exchange on the server so the secret never reaches the browser.
Q: Can I restrict Google sign-in to my company's Workspace domains?
Yes. Enter one or more domains in Permitted Workspace Domains. Only Google accounts belonging to a listed domain can sign in; this includes blocking personal Gmail accounts.
Q: Does a Google group name need to match Group Mappings exactly?
No, letter case is ignored for Google. Google Workspace always returns group email addresses in lowercase, so a mapping entered as OpCon-Admins@acme.com still matches the group returned by Google. For every other provider, the match is exact.
Q: Which privilege is required to configure SSO?
You must have the Role_ocadm role or the Maintain Server Options function privilege.
Q: What happens to a user's OpCon password after they first log in through SSO?
Once a user accesses Solution Manager through SSO, their OpCon password automatically changes to a random value, ensuring SSO becomes the only means of authentication for that user going forward.
Glossary
Enterprise Manager (EM): OpCon's rich client graphical user interface for Windows and Linux, used to define schedules and jobs, manage automation data, and perform operational tasks.
Solution Manager: OpCon's browser-based graphical user interface for managing automation data, performing operational actions, and administering the system.
Token (Global Property): A named value stored in the OpCon database, referenced in job definitions and events using [[PropertyName]] syntax. Tokens pass dynamic values — such as dates, file paths, or counts — into automation workflows.
Resource: A numeric variable in OpCon representing a finite pool. Jobs can be configured to require a set number of resource units to run, limiting concurrent executions and preventing resource contention.
Role: A named security profile in OpCon that groups privileges together. Roles are assigned to user accounts to control which features, schedules, jobs, machines, and administrative functions a user can access.
Privilege: A specific permission granted through an OpCon role that controls access to a feature, function, or object type. Privileges are organized into categories such as Function Privileges, Machine Privileges, Schedule Privileges, and Access Codes.
OpCon: Continuous' workflow automation platform. The OpCon server includes the database, SAM and Supporting Services (SAM-SS), and graphical user interfaces. agents installed on target platforms run jobs and report results.