Okta
Urengi reads the app inventory Okta already sees, so a shadow vendor surfaces the day someone gets a login instead of at renewal. Assignments tell you how many people are exposed before you decide how hard to look.
- Category
- Identity & SSO
- Auth method
- OAuth 2.0
- Direction
- Read-only
- Sync frequency
- Every 15 minutes
- Scopes requested
- 4
- Available on
- All plans
- Maintained by
- Urengi
- of new vendors found here first
- 61%
- median time to connect
- 3 min
- scopes requested, all read-only
- 4
- writes back into Okta, ever
- 0
What the Okta integration does
Three reads that turn your identity provider into a vendor discovery tool.
The app inventory, as a vendor list
Every application in the Okta org is matched against vendors already under review. Anything unmatched is queued for intake with its first sign-in date attached.
Assignment counts feed the tier
A tool with four users and one with four hundred are not the same risk. Assignment counts land on the review as an input the score can actually cite.
Deprovisioning that gets noticed
An app that loses every assignment is probably a vendor you stopped paying for. Urengi flags it for offboarding rather than renewing the review forever.
Exactly what Urengi can see
Four scopes, all read-only. Urengi never writes to your identity provider.
Urengi reads
- Application names, labels and sign-on modes
- Assignment counts per application
- Group names and membership
- User display names and work emails
Urengi writes
- Nothing — this connection is read-only
Urengi never touches
- Credentials, MFA factors or session tokens
- Policies, rules or the sign-on config
- System logs beyond application events
- Anything after you revoke the token
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Okta from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Okta token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Okta and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Okta
- one click, no ticket
- EU or US residency
- chosen at signup