Reference
Complete API endpoint reference, error code catalog, feature matrix, and platform limitations for Hawiyati IAM.
Complete API endpoint reference, error code catalog, feature matrix, and platform limitations for Hawiyati IAM.
Complete API endpoint reference, error code catalog, feature matrix, and platform limitations for Hawiyati IAM.
The sections below cover the complete API endpoint reference, error codes, feature matrix, and platform limitations. For a full module map with ports, gRPC boundaries, and deployment topology, see the Implementation Guide.
API Overview
Hawiyati exposes several distinct API surfaces, each with its own port, authentication mechanism, and purpose. All production endpoints must be served over HTTPS.
| API Surface | Port | Authentication | Base URL | Purpose |
|---|---|---|---|---|
| IdP HTTP Server | 8085 |
Session cookie / browser flow | https://idp.hawiyati.org |
SAML, OIDC, login UI, registration flows |
| Gateway | 8080 |
Pass-through | https://idp.hawiyati.org:8080 |
Spring Cloud Gateway routing layer |
| Admin Console API | 8095 |
Admin session cookie (SUPER_ADMIN / ADMIN / VIEWER role) | https://admin.hawiyati.org:8095 |
User management, SP config, policy management, audit logs |
| SCIM 2.0 API | 8098 |
HTTP Bearer token (generated in admin console) | https://idp.hawiyati.org:8098/scim/v2 |
Inbound user/group provisioning from enterprise IdM systems |
| Federation gRPC | 8087 |
mTLS (pending production hardening) | Internal only | SAML/OIDC orchestration between internal services |
Versioning Policy
Hawiyati does not currently publish a versioned REST API contract for admin or SCIM surfaces. Breaking changes are communicated via release notes. The SCIM 2.0 API follows RFC 7643 / RFC 7644 schema versioning. OIDC and SAML endpoints follow their respective protocol specifications and do not carry version prefixes.
Content Types
| Surface | Request Content-Type | Response Content-Type |
|---|---|---|
| Admin API | application/json | application/json |
| SCIM 2.0 | application/scim+json | application/scim+json |
| OIDC Token endpoint | application/x-www-form-urlencoded | application/json |
| SAML SSO/SLO | URL-encoded form or HTTP redirect | HTML (browser redirect) or XML |
Rate Limiting
Rate limiting is enforced at the gateway and per-endpoint level. When a limit is exceeded the server returns 429 Too Many Requests with the following headers:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Retry-After | Seconds to wait before retrying |
application.yml under hawiyati.rate-limit.*. SMS OTP and FIDO2 registration endpoints have tighter per-MSISDN and per-user limits independent of the global threshold.
SAML Endpoints
Hawiyati implements a custom SAML 2.0 stack (not OpenSAML). All SAML endpoints are served on port 8085. The IdP only — Hawiyati does not act as a SAML SP.
https://idp.hawiyati.org — replace with your configured hostname. In dev: https://dev.hawiyati.org:8085
| Endpoint | Method | Description | Notes |
|---|---|---|---|
/saml/metadata |
GET | IdP metadata XML — contains EntityID, SSO/SLO locations, signing certificate | Publicly accessible. SP must import this to establish trust. Refresh after certificate rollover. |
/saml/sso |
GET | SSO entry point — HTTP-Redirect binding | SP sends SAMLRequest (base64-deflated) + optional RelayState + SigAlg + Signature as query params |
/saml/sso |
POST | SSO entry point — HTTP-POST binding | SP sends SAMLRequest (base64) + optional RelayState in POST body. Less common but supported. |
/saml/slo |
GET | Single Logout — HTTP-Redirect binding | SP or IdP initiates SLO. Carries SAMLRequest or SAMLResponse + RelayState. Propagates logout to all active SPs in the session. |
/saml/slo |
POST | Single Logout — HTTP-POST binding | Same as GET variant but using POST binding for the SLO message. |
/saml/acs |
N/A | Not an IdP endpoint | The Assertion Consumer Service (ACS) is a SP endpoint. Hawiyati POSTs assertions to the SP's registered ACS URL. |
SAML Request Parameters
| Parameter | Required | Description |
|---|---|---|
| SAMLRequest | required | Base64-encoded (and deflated for redirect binding) AuthnRequest XML |
| RelayState | optional | Opaque SP state string, max 80 bytes, returned unchanged in the response |
| SigAlg | conditional | Required when SP signs requests — algorithm URI e.g. http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 |
| Signature | conditional | Base64-encoded signature over the query string (when SP request signing enabled) |
SAML Assertion Attributes
The IdP includes the following attributes in the assertion by default. Attribute mapping is configurable per SP in the admin console.
| Attribute Name | NameFormat | Value Example |
|---|---|---|
NameID | emailAddress / persistent (configurable) | [email protected] or opaque UUID |
email | urn:oasis:names:tc:SAML:2.0:attrname-format:basic | [email protected] |
groups | urn:oasis:names:tc:SAML:2.0:attrname-format:basic | Multi-value: staff, admins |
assurance_level | urn:oasis:names:tc:SAML:2.0:attrname-format:basic | L1, L2, L3, L4 |
phone_number | urn:oasis:names:tc:SAML:2.0:attrname-format:basic | +2135XXXXXXXX (E.164) |
OIDC Endpoints
Hawiyati implements a custom OIDC stack (not Nimbus) supporting Authorization Code + PKCE with RS256 tokens. All OIDC endpoints are served on port 8085.
https://idp.hawiyati.org/.well-known/openid-configuration. Always use the discovery document to obtain endpoint URLs — do not hard-code them.
| Endpoint | Method | Description | Key Parameters |
|---|---|---|---|
/.well-known/openid-configuration |
GET | OIDC Discovery document — lists all endpoints, scopes, signing algorithms | No parameters. Public. Cache with short TTL. |
/oauth2/authorize |
GET | Authorization endpoint — initiates the Authorization Code flow | response_type=code, client_id, redirect_uri, scope, state, nonce, code_challenge, code_challenge_method=S256 |
/oauth2/token |
POST | Token endpoint — exchange authorization code for tokens, or refresh tokens | grant_type, code, redirect_uri, client_id, code_verifier (PKCE); or grant_type=refresh_token, refresh_token |
/oauth2/userinfo |
GET | UserInfo endpoint — returns claims for the authenticated user | Bearer token in Authorization header. Returns JSON with claims matching token scopes. |
/oauth2/jwks |
GET | JSON Web Key Set — RS256 public keys for token signature verification | No parameters. Public. Cache for up to 1 hour; re-fetch on unknown kid. |
/oauth2/revoke |
POST | Token revocation — invalidates a refresh or access token | token, token_type_hint (optional: refresh_token or access_token), client_id |
/oauth2/logout |
GET | RP-initiated logout — clears IdP session and optionally redirects | id_token_hint, post_logout_redirect_uri, state |
Supported Scopes
| Scope | Claims Returned |
|---|---|
openid | sub, iss, aud, exp, iat (always required) |
profile | name, given_name, family_name, preferred_username |
email | email, email_verified |
phone | phone_number, phone_number_verified |
groups | groups (array of group names) |
assurance | assurance_level (L0–L4 string) |
ID Token Validation Steps
Relying parties must validate the ID token before trusting any claims:
- Verify the
issclaim matches your configured OIDC issuer URL. - Verify the
audclaim contains yourclient_id. - Verify the token is not expired (
exp> current time). - Verify the RS256 signature using the public key from
/oauth2/jwks, matching bykid. - Verify the
nonceclaim matches the nonce you sent (if you sent one). - If using PKCE: verify the token exchange used the correct
code_verifier.
PKCE Explanation
PKCE (Proof Key for Code Exchange, RFC 7636) prevents authorization code interception attacks. The client generates a random code_verifier (43–128 chars), computes code_challenge = BASE64URL(SHA-256(code_verifier)), and includes the challenge in the authorization request. The verifier is sent at token exchange time; the server recomputes the hash and rejects mismatches.
# Example authorization URL
GET /oauth2/authorize
?response_type=code
&client_id=my-app
&redirect_uri=https%3A%2F%2Fapp.example.com%2Fcallback
&scope=openid%20profile%20email%20groups
&state=random-state-value
&nonce=random-nonce-value
&code_challenge=dBjftJeZ4CVP-mB92K27uhbUJU1p1r_wW1gFWFOEjXk
&code_challenge_method=S256
SCIM 2.0 Endpoints
Hawiyati implements a SCIM 2.0 server (port 8098) for inbound provisioning, and a SCIM 2.0 outbound push client for lifecycle fan-out to downstream applications. The SCIM server accepts provisioning requests from enterprise IdM systems (e.g., Entra ID, Okta, SailPoint).
/scim/v2/Groups and /scim/v2/Groups/{id} are fully implemented (RFC 7643/7644). PATCH operations validate op and path; unrecognized combinations return 400 invalidSyntax per RFC 7644 §3.5.2.
| Endpoint | Methods | Description |
|---|---|---|
/scim/v2/Users |
GET POST | List users (with filter, startIndex, count params) or create a new user |
/scim/v2/Users/{id} |
GET PATCH DELETE | Retrieve, partially update (PATCH operations), or deactivate/delete a specific user |
/scim/v2/Groups |
GET POST | List groups (paged) or create a new group with optional members |
/scim/v2/Groups/{id} |
GET PUT PATCH DELETE | Retrieve, replace, partially update (add/remove/replace members, rename), or delete a group. Unrecognized PATCH op/path returns 400 invalidSyntax. |
/scim/v2/ServiceProviderConfig |
GET | SCIM server capability declaration (RFC 7643 §5). Lists supported operations, authentication schemes, bulk/filter/sort support. |
/scim/v2/Schemas |
GET | SCIM schema definitions for User and enterprise extension |
SCIM User Schema
Supported core attributes from RFC 7643:
| Attribute | Type | Notes |
|---|---|---|
| userName | String | Unique identifier within Hawiyati. Maps to users.username. |
| name.formatted | String | Full display name |
| name.givenName | String | First name |
| name.familyName | String | Last name |
| emails | Multi-value | At least one primary:true email required for invite flows |
| phoneNumbers | Multi-value | Must be E.164 format (+2135XXXXXXXX) for SMS OTP to function |
| active | Boolean | Setting false deactivates the account (users.active = false) |
| externalId | String | Source system identifier — stored in users.external_id |
Enterprise Extension
Schema URI: urn:ietf:params:scim:schemas:extension:hawiyati:2.0:User
| Extension Field | Type | Description |
|---|---|---|
| sourceInstanceId | String | Identifies the source IdM instance — allows multi-system provisioning without externalId collision |
| pendingApproval | Boolean | Read-only in SCIM response — reflects the users.pending_approval flag |
SCIM Provisioning Flow
When a SCIM POST creates a new user, the account is placed in MIGRATED_UNCLAIMED state (active=false, pendingApproval=true). The user must claim their account via the claim link before they can authenticate. The claim token (256-bit random, HMAC-SHA256 stored, 15-minute TTL, single-use) is generated automatically and can be dispatched via the admin console.
Admin API Reference
The admin REST API is served on port 8095 and requires an authenticated admin session (HTTP session cookie). All endpoints require at minimum ADMIN role; destructive operations require SUPER_ADMIN.
/admin/login. The server sets an HttpOnly; Secure; SameSite=Strict session cookie. Include the cookie on all subsequent requests. Admin sessions expire after the configured TTL (default: 30 minutes idle).
User Management
| Endpoint | Method | Description | Key Params / Body |
|---|---|---|---|
/admin/api/users |
GET | List users — paginated | Query: status, group, source (LOCAL/LDAP/SQL), search (username/email), page, size |
/admin/api/users |
POST | Create user | Body: username, email or phoneNumber (E.164), password (plain — hashed Argon2id on save), optional groups[] |
/admin/api/users/{id} |
GET | Get user details | Returns full user profile including status flags, groups, assurance level, MFA methods enrolled |
/admin/api/users/{id} |
PATCH | Update user fields | Partial update — send only fields to change. Cannot update credential hashes directly. |
/admin/api/users/{id} |
DELETE | Delete user (SUPER_ADMIN only) | Hard delete — irreversible. Generates audit event. |
/admin/api/users/{id}/activate |
POST | Activate account — sets active=true |
No body required. Generates AUTH audit event. |
/admin/api/users/{id}/deactivate |
POST | Deactivate account — sets active=false |
Immediately terminates active sessions. Body optional: reason string. |
/admin/api/users/{id}/approve |
POST | Clear pending approval — sets pendingApproval=false |
Moves ACTIVE_LIMITED → ACTIVE. No body required. |
/admin/api/users/{id}/reset-password |
POST | Trigger password reset email | Sends one-time reset link to the user's registered email address. |
/admin/api/users/{id}/unlock |
POST | Unlock account after lockout | Clears failed-attempt counter. Generates audit event. |
/admin/api/users/{id}/resend-claim |
POST | Re-send claim token to MIGRATED_UNCLAIMED user | Generates a new claim token (invalidates any existing token). Sends via email or SMS. |
Audit Logs
| Endpoint | Method | Description | Key Params |
|---|---|---|---|
/admin/api/audit-logs |
GET | Search audit logs — paginated | from / to (ISO-8601), service, category (AUTH/ADMIN/SESSION/KYC/SCIM), action, outcome (SUCCESS/FAILURE), actorId, page, size |
/admin/api/audit-logs/export |
POST | Export audit log subset as CSV or JSON | Body: same filters as search + format (csv/json). Max 50,000 rows per export. |
Service Provider Management
| Endpoint | Method | Description |
|---|---|---|
/admin/api/service-providers | GET | List all registered SPs (SAML + OIDC) |
/admin/api/service-providers | POST | Register a new SP — body includes protocol, EntityID/clientId, redirect URLs, attribute mapping |
/admin/api/service-providers/{id} | GET | Get SP configuration details |
/admin/api/service-providers/{id} | PATCH | Update SP configuration |
/admin/api/service-providers/{id} | DELETE | Remove SP registration — SUPER_ADMIN only |
HTTP Status Codes
| Status | Meaning | When Returned |
|---|---|---|
200 OK | Success | Successful GET, PATCH response with body |
201 Created | Resource created | Successful POST (user created, SP registered) |
204 No Content | Success, no body | Successful DELETE or action endpoints (activate, approve) |
400 Bad Request | Invalid request | Missing required field, malformed JSON, invalid parameter value |
401 Unauthorized | Authentication required | No session cookie, expired session, invalid SCIM bearer token |
403 Forbidden | Insufficient permissions | Role too low for the operation (e.g., VIEWER attempting write) |
404 Not Found | Resource not found | User ID, SP ID, or endpoint does not exist |
409 Conflict | Resource conflict | Username or email already exists; SCIM duplicate externalId |
422 Unprocessable Entity | Validation error | Field value fails validation (e.g., invalid E.164 phone, weak password) |
429 Too Many Requests | Rate limit exceeded | Too many login attempts, OTP requests, or API calls in window |
500 Internal Server Error | Server error | Unexpected exception — check application logs |
503 Service Unavailable | Dependency down | PostgreSQL or Redis unreachable; downstream service timeout |
SAML Status Codes
SAML protocol errors are returned in the <samlp:StatusCode> element of the Response.
| Status Code | Meaning | Common Cause |
|---|---|---|
urn:oasis:…:Success | Authentication successful | Normal success response |
urn:oasis:…:Requester | Error in the SP's request | Malformed AuthnRequest, unsupported NameID format, missing required element |
urn:oasis:…:Responder | Error on the IdP side | Internal Hawiyati error, DB connectivity issue |
urn:oasis:…:VersionMismatch | Wrong SAML version | SP sending SAML 1.1 to a SAML 2.0 endpoint |
urn:oasis:…:AuthnFailed | Authentication failed | Wrong credentials, account locked, MFA failed |
urn:oasis:…:NoAuthnContext | Cannot satisfy AuthnContext | SP requests assurance level the user does not have |
urn:oasis:…:RequestDenied | Request denied by policy | Auth policy evaluates to DENY for this user/SP combination |
OIDC Error Codes
OIDC errors are returned as JSON with error and error_description fields per RFC 6749.
| Error Code | Description | Common Fix |
|---|---|---|
invalid_request | Missing or malformed parameter | Check that all required params are present and URL-encoded correctly |
invalid_client | Client authentication failed | Verify client_id is registered in Hawiyati admin console |
invalid_grant | Authorization code invalid, expired, or already used | Exchange the code immediately after redirect; codes are single-use |
unauthorized_client | Client not permitted for this grant type | Verify the client's allowed grant types in admin console |
unsupported_grant_type | Grant type not supported | Hawiyati supports authorization_code and refresh_token only |
invalid_scope | Requested scope not allowed | Verify the scope is registered for the client; remove unsupported scopes |
redirect_uri_mismatch | Redirect URI not registered | Add the exact redirect URI (including query string if any) to client config |
code_challenge_failed | PKCE verifier does not match challenge | Ensure code_verifier is the original random string, not re-hashed |
server_error | Unexpected IdP error | Check Hawiyati application logs; report with request timestamp and client_id |
temporarily_unavailable | IdP temporarily down or overloaded | Implement retry with exponential backoff; check Retry-After header |
SCIM Error Types
SCIM errors follow RFC 7644 §3.12 and are returned as application/scim+json with schemas, detail, and scimType fields.
| scimType | HTTP Status | Meaning |
|---|---|---|
invalidFilter | 400 | Filter expression syntax error or unsupported attribute |
tooMany | 400 | Too many results — narrow the filter or use pagination |
uniqueness | 409 | Attribute value must be unique — username or externalId already exists |
mutability | 400 | Attempt to modify a read-only attribute (e.g., id, meta) |
invalidSyntax | 400 | JSON body does not conform to SCIM schema |
invalidPath | 400 | PATCH path references an attribute that does not exist |
noTarget | 400 | PATCH filter matched no values |
invalidValue | 400 | Attribute value is invalid (e.g., non-E.164 phone number) |
invalidVers | 400 | ETag version mismatch in conditional update |
sensitive | 403 | Attempt to provision a sensitive field (credentials, assurance level) — not allowed via SCIM |
Feature Matrix
Current platform capability status as of Hawiyati 1.x (Flyway head: V62).
| Feature / Capability | Status | Notes |
|---|---|---|
| SAML 2.0 SSO | Available | SP-initiated SSO and IdP metadata. HTTP-Redirect and HTTP-POST bindings. |
| SAML 2.0 SLO | Available | Single Logout chain across all active SP sessions. Validate end-to-end per SP. |
| OIDC Authorization Code + PKCE | Available | RS256 signed ID tokens. Custom OIDC stack (not Nimbus). Federation service issuer. |
| OIDC Front/Back-Channel Logout | Available | RP-initiated, front-channel, and back-channel logout all implemented (2026-06-20). Configures via frontchannel_logout_uri / backchannel_logout_uri on the SP registration. |
| Password Authentication | Available | LOCAL and LDAP user stores. Argon2id hashing. SQL store bridge pending. |
| TOTP (RFC 6238) | Available | 30-second codes. Replay protection. TOTP secret encrypted at rest. Admin and end-user enrollment flows. |
| Email OTP | Available | MFA, registration, and password reset flows. 5-minute TTL. SMTP gateway required. |
| SMS OTP | Available | Generic HTTP SMS gateway. Per-MSISDN rate limiting. E.164 phone number required. |
| FIDO2 / WebAuthn / Passkeys | Available | Public key stored; private key never leaves device. Platform + hardware authenticators. Verify full production test coverage before go-live. |
| Self-Service Registration | Available | Email/phone verification. L0 account on completion. Policy-configurable attributes. |
| SP-Initiated Registration | Available | SP sends user to registration with continuation token. Completion token returned to SP after registration. |
| Enterprise Account Claim | Available | SCIM provision → MIGRATED_UNCLAIMED → claim token → user claims account. Claim token: 256-bit random, HMAC-SHA256, 15-min TTL, single-use. |
| Password Reset | Available | Email OTP flow. Requires registered email address. |
| Account Portal (Self-Service) | Available | 9-page portal as of 2026-06-12. Profile, MFA management, session management, passkeys. |
| Admin Console — Users & Groups | Available | CRUD operations, group assignment, status management, bulk import. |
| Authentication Policies | Available | Rule-based, first-match evaluation. Conditions: group, network zone, time window. Actions: ALLOW/MFA_REQUIRED/MFA_STRONG/DENY. |
| Adaptive Risk Engine | Available | OFF/MONITOR/ENFORCE modes. Signals: NEW_DEVICE, velocity, GeoIP, IP reputation. Score 0–100 → LOW/MEDIUM/HIGH/CRITICAL. |
| Audit Log Search & Export | Available | DB-backed search with filters. CSV and JSON export (max 50,000 rows). CSV hardening pending. |
| LDAP / AD Authentication & Sync | Available | Users, groups, and memberships. Configurable bind DN, search filter, attribute mapping. |
| SCIM 2.0 Users (Inbound) | Available | CRUD and limited PATCH operations. Filters partially supported. |
| SCIM 2.0 Groups (Inbound) | Pending | Endpoint returns 501. Planned in next minor release. |
| External SQL User Stores | Partial | PostgreSQL SQL store: configurable, testable, sync available. Activation pending. MySQL/MSSQL drivers not yet bundled. |
| KYC — Basic / Standard (L1/L2) | Available | OCR/MRZ document capture. Standard adds selfie + face match. Document fingerprinting (HMAC-SHA256). |
| KYC — Strong / High Assurance (L3/L4) | Pending | Workflow implemented. Frozen pending biometric partner approval. Source of truth: kyc_profiles.current_level. |
| gRPC mTLS | Pending | Required for production inter-service security. Hardening in progress. |
| Login Lockout Enforcement | Available | Shipped 2026-06-16. LoginAttemptRecorder.isLockedOut() gates the username phase. Configurable maxLoginAttempts / lockoutMinutes via InstanceSettings. |
| Backup Automation | Pending | Runbook documented. Automated tooling pending. |
| AD / Kerberos Connector | Roadmap | Native Kerberos pass-through authentication. 28–36 month enterprise moat item. |
| WS-Federation | Roadmap | For legacy .NET / SharePoint SP integration. |
| RADIUS | Roadmap | For VPN and network device MFA integration. |
| SCIM Outbound | Roadmap | Push identity changes to downstream systems. Currently inbound only. |
| Connector Catalog | Roadmap | Pre-built connectors for common enterprise applications. |
Known Limitations
Authentication & Federation
- No IdP-initiated OIDC flow — Hawiyati supports SP-initiated flows only. IdP-initiated OIDC is not on the near-term roadmap.
- No JWT profile for SAML — SAML assertions are XML only; no SAML-to-JWT bridge.
- OIDC front/back-channel logout incomplete — RP-initiated logout works; propagation to all RP sessions via back-channel is partial.
- No IdP-initiated SAML by default — IdP-initiated SSO can be enabled per SP but is discouraged due to CSRF exposure.
Provisioning
- SCIM Groups endpoint returns 501 — Group management via SCIM is not yet implemented. Use admin API.
- SCIM is inbound only — Hawiyati does not push provisioning events to downstream systems.
- SCIM filter support is limited — Complex filter expressions (nested AND/OR) may return 400. Use simple
eqfilters.
KYC / Biometrics
- L3/L4 KYC frozen — The Strong and High Assurance workflows are implemented but held pending biometric partner approval.
kyc_profiles.current_levelwill not advance beyond L2 until the freeze is lifted. - Notification delivery TBC — KYC decision email templates exist but automatic delivery is not a verified trigger. Define operational notification ownership before launch.
Infrastructure
- gRPC mTLS not yet enforced — Internal service-to-service communication uses plaintext gRPC in the current build. mTLS hardening is required before production deployment.
- Login lockout enforced — Shipped 2026-06-16. Configurable attempt limit and lockout window via admin Settings.
- Backup automation manual — Only a runbook exists; automated scheduling is pending.
Roadmap
The following capabilities are planned but not yet implemented. Timelines are indicative and subject to change.
| Capability | Target Horizon | Notes |
|---|---|---|
| SCIM Groups inbound | Near-term | Next minor release. Required for group-based access policies via SCIM provisioning. |
| Login lockout enforcement | Shipped 2026-06-16 | Available. Configurable via admin Settings. |
| gRPC mTLS | Near-term | Required for production. Certificate provisioning and config underway. |
| KYC L3/L4 (biometric) | Medium-term | Pending biometric partner integration approval and liveness vendor selection. |
| OIDC back-channel logout | Shipped 2026-06-20 | Available. Configure backchannel_logout_uri on the SP registration. |
| AD / Kerberos connector | 28–36 months | Enterprise moat item. Native Kerberos pass-through for domain-joined clients. |
| WS-Federation | 28–36 months | Legacy .NET and SharePoint integration. |
| RADIUS | 28–36 months | VPN and network access MFA. |
| SCIM outbound provisioning | 28–36 months | Push identity events to downstream systems. |
| Connector catalog | 28–36 months | Pre-built SP connectors for common enterprise SaaS applications. |
| Backup automation | Near-term | Scheduled PostgreSQL + Redis backup with verification and alerting. |
docs/SESSION_STATE.md for updates to this roadmap. The feature matrix above is updated with each release.