Public sector · Legacy and infrastructure
CA Top Secret user provisioning with Okta
Broadcom mainframe security product that manages user accessor IDs and resource access on z/OS. CA Top Secret has no SCIM provisioning, per the source below.
More state government apps →What Okta covers for CA Top Secret, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the CA Top Secret account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for CA Top Secret.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to CA Top Secret with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares CA Top Secret logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the CA Top Secret account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes CA Top Secret roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes CA Top Secret access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in CA Top Secret. | Changes the CA Top Secret password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove CA Top Secret accounts. | Pulls the CA Top Secret user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside CA Top Secret. | Step level evidence for every action StitchOps takes in CA Top Secret. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to CA Top Secret with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares CA Top Secret logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the CA Top Secret account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes CA Top Secret roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes CA Top Secret access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in CA Top Secret.
StitchOps
Changes the CA Top Secret password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove CA Top Secret accounts.
StitchOps
Pulls the CA Top Secret user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside CA Top Secret.
StitchOps
Step level evidence for every action StitchOps takes in CA Top Secret.
Okta coverage from the Okta Integration Network, read October 20, 2026. CA Top Secret has no OIN listing. StitchOps for Okta →
SCIM and Okta status
What CA Top Secret supports today.
CA Top Secret has no SCIM provisioning, per the source below. Accounts are managed in the system itself.
- SCIM status
- No SCIM
- Okta Integration Network
- Not in the Okta Integration Network. Read October 20, 2026.
- Vendor
- Broadcom
- Deployment
- Mainframe
Last verified 2026-10-20.Sources:Product pageAccount administration documentationOkta Integration Network
More state government apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in CA Top Secret.
StitchOps creates, changes, suspends and removes Top Secret ACIDs, and pulls the user list for access reviews. The StitchOps worker runs inside your environment, and your data never leaves your network or key vault.
Joiners
Create the CA Top Secret account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change CA Top Secret roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in CA Top Secret on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to CA Top Secret on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does CA Top Secret support SCIM?
CA Top Secret has no SCIM provisioning, per the source below. Accounts are managed in the system itself.
Can CA Top Secret accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes CA Top Secret accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is CA Top Secret in the Okta Integration Network?
No. As of October 20, 2026, the OIN has no listing for CA Top Secret. Okta can sign users in only through a custom app if CA Top Secret supports SAML or OIDC, and has no connector to manage CA Top Secret accounts.
Can Okta deprovision CA Top Secret users?
Not through an OIN connector. StitchOps removes CA Top Secret accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate CA Top Secret passwords when someone leaves?
StitchOps logs in to CA Top Secret, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.