Overview
Connect Okta, map claims to roles, and test sign-in.
Prerequisites
- Okta admin privileges
Permissions required
Steps (4)
-
1
Create Okta app integration
In Okta, create an OIDC or SAML app; collect Issuer, Client ID/Secret or download IdP metadata.
Tips
—
Validation
—
Success criteria
—
-
2
Add provider in AccessGuard
Settings → SSO → Add Provider → Okta. Paste credentials or upload metadata.
Tips
—
Validation
- Discovery/JWKS validates successfully.
Success criteria
—
-
3
Map groups/claims to roles
Define rules, e.g., okta.groups contains “Admins” → role: admin.
Tips
—
Validation
—
Success criteria
- Test user signs in and receives correct role.
-
4
Enable JIT/SCIM (optional)
Turn on JIT provisioning; optionally configure SCIM for lifecycle.
Tips
—
Validation
—
Success criteria
—
About this guide
AccessGuard secures apps and external sites with hosted authentication and short-lived JWTs. Enable MFA, define RBAC permissions, and connect enterprise identity via SAML or OIDC. A lightweight HMAC bridge lets you embed login, registration, and token refresh flows on any domain without CORS pain.
Admins manage users, sessions, connections, and policies from one console. Profiles consolidate verified emails/phones, consents, KYC docs, and risk flags. Events and metrics provide visibility for security and ops.
Designed for velocity and safety: opinionated defaults, least-privilege keys, Prometheus counters, and exportable audit logs.