H· Hawiyati Documentation

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.

Hawiyati IAM Platform — Component Architecture HAWIYATI IAM PLATFORM — COMPONENT ARCHITECTURE Spring Boot 3.5 · Java 25 · gRPC EXTERNAL ACTORS ENTRY LAYER & FEDERATION HTTPS · SAML 2.0 · OIDC · WebAuthn PLATFORM SERVICES HTTPS internal · gRPC DATA & INFRASTRUCTURE JDBC · Redis pub/sub · gRPC User Browser Browser · Mobile App Administrator Admin Console SAML Service Provider SAML 2.0 OIDC Relying Party OIDC · OAuth 2.0 SCIM Client HR System · Directory hawiyati-gateway Spring Cloud Gateway · :8080 Routing · TLS termination hawiyati-http-server IdP Login · MFA · FIDO2 · :8085 SAML ACS · OIDC callback · Account BFF hawiyati-federation SAML 2.0 · OIDC · :8087 Assertion & token issuance · Policy hawiyati-admin Admin Console · :8095 · WebFlux hawiyati-account Account Portal · :8096 · BFF/OIDC hawiyati-scim SCIM 2.0 API · :8098 hawiyati-session · :9004 hawiyati-cache · :9003 hawiyati-infra · :9002 PostgreSQL hawiyati · hawiyati_identity Redis / Valkey Sessions · Cache · Rate limits Audit & Logs CEF Syslog · OTel · SIEM PKI & Keystore SAML · OIDC · mkcert TLS External Actor External System Entry / Federation Platform Service gRPC Service Data Store

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

SurfaceRequest Content-TypeResponse Content-Type
Admin APIapplication/jsonapplication/json
SCIM 2.0application/scim+jsonapplication/scim+json
OIDC Token endpointapplication/x-www-form-urlencodedapplication/json
SAML SSO/SLOURL-encoded form or HTTP redirectHTML (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:

HeaderMeaning
X-RateLimit-LimitMaximum requests allowed in the window
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp when the window resets
Retry-AfterSeconds to wait before retrying
Note Default rate limit thresholds are configured in 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.

Base URL https://idp.hawiyati.org — replace with your configured hostname. In dev: https://dev.hawiyati.org:8085
EndpointMethodDescriptionNotes
/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

ParameterRequiredDescription
SAMLRequestrequiredBase64-encoded (and deflated for redirect binding) AuthnRequest XML
RelayStateoptionalOpaque SP state string, max 80 bytes, returned unchanged in the response
SigAlgconditionalRequired when SP signs requests — algorithm URI e.g. http://www.w3.org/2001/04/xmldsig-more#rsa-sha256
SignatureconditionalBase64-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 NameNameFormatValue Example
NameIDemailAddress / persistent (configurable)[email protected] or opaque UUID
emailurn:oasis:names:tc:SAML:2.0:attrname-format:basic[email protected]
groupsurn:oasis:names:tc:SAML:2.0:attrname-format:basicMulti-value: staff, admins
assurance_levelurn:oasis:names:tc:SAML:2.0:attrname-format:basicL1, L2, L3, L4
phone_numberurn: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.

Discovery Document All OIDC metadata is published at https://idp.hawiyati.org/.well-known/openid-configuration. Always use the discovery document to obtain endpoint URLs — do not hard-code them.
EndpointMethodDescriptionKey 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

ScopeClaims Returned
openidsub, iss, aud, exp, iat (always required)
profilename, given_name, family_name, preferred_username
emailemail, email_verified
phonephone_number, phone_number_verified
groupsgroups (array of group names)
assuranceassurance_level (L0–L4 string)

ID Token Validation Steps

Relying parties must validate the ID token before trusting any claims:

  1. Verify the iss claim matches your configured OIDC issuer URL.
  2. Verify the aud claim contains your client_id.
  3. Verify the token is not expired (exp > current time).
  4. Verify the RS256 signature using the public key from /oauth2/jwks, matching by kid.
  5. Verify the nonce claim matches the nonce you sent (if you sent one).
  6. 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 Groups — fully implemented /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.
EndpointMethodsDescription
/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:

AttributeTypeNotes
userNameStringUnique identifier within Hawiyati. Maps to users.username.
name.formattedStringFull display name
name.givenNameStringFirst name
name.familyNameStringLast name
emailsMulti-valueAt least one primary:true email required for invite flows
phoneNumbersMulti-valueMust be E.164 format (+2135XXXXXXXX) for SMS OTP to function
activeBooleanSetting false deactivates the account (users.active = false)
externalIdStringSource system identifier — stored in users.external_id

Enterprise Extension

Schema URI: urn:ietf:params:scim:schemas:extension:hawiyati:2.0:User

Extension FieldTypeDescription
sourceInstanceIdStringIdentifies the source IdM instance — allows multi-system provisioning without externalId collision
pendingApprovalBooleanRead-only in SCIM response — reflects the users.pending_approval flag
Explicitly Not Supported via SCIM The following fields are NOT accepted in SCIM requests and will be rejected or silently ignored: password hashes, MFA enrollment data, assurance level, KYC status, session data. These are managed exclusively through Hawiyati's own credential and KYC workflows.

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.

Authentication Obtain a session by POSTing credentials to /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

EndpointMethodDescriptionKey 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

EndpointMethodDescriptionKey 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

EndpointMethodDescription
/admin/api/service-providersGETList all registered SPs (SAML + OIDC)
/admin/api/service-providersPOSTRegister a new SP — body includes protocol, EntityID/clientId, redirect URLs, attribute mapping
/admin/api/service-providers/{id}GETGet SP configuration details
/admin/api/service-providers/{id}PATCHUpdate SP configuration
/admin/api/service-providers/{id}DELETERemove SP registration — SUPER_ADMIN only

HTTP Status Codes

StatusMeaningWhen Returned
200 OKSuccessSuccessful GET, PATCH response with body
201 CreatedResource createdSuccessful POST (user created, SP registered)
204 No ContentSuccess, no bodySuccessful DELETE or action endpoints (activate, approve)
400 Bad RequestInvalid requestMissing required field, malformed JSON, invalid parameter value
401 UnauthorizedAuthentication requiredNo session cookie, expired session, invalid SCIM bearer token
403 ForbiddenInsufficient permissionsRole too low for the operation (e.g., VIEWER attempting write)
404 Not FoundResource not foundUser ID, SP ID, or endpoint does not exist
409 ConflictResource conflictUsername or email already exists; SCIM duplicate externalId
422 Unprocessable EntityValidation errorField value fails validation (e.g., invalid E.164 phone, weak password)
429 Too Many RequestsRate limit exceededToo many login attempts, OTP requests, or API calls in window
500 Internal Server ErrorServer errorUnexpected exception — check application logs
503 Service UnavailableDependency downPostgreSQL or Redis unreachable; downstream service timeout

SAML Status Codes

SAML protocol errors are returned in the <samlp:StatusCode> element of the Response.

Status CodeMeaningCommon Cause
urn:oasis:…:SuccessAuthentication successfulNormal success response
urn:oasis:…:RequesterError in the SP's requestMalformed AuthnRequest, unsupported NameID format, missing required element
urn:oasis:…:ResponderError on the IdP sideInternal Hawiyati error, DB connectivity issue
urn:oasis:…:VersionMismatchWrong SAML versionSP sending SAML 1.1 to a SAML 2.0 endpoint
urn:oasis:…:AuthnFailedAuthentication failedWrong credentials, account locked, MFA failed
urn:oasis:…:NoAuthnContextCannot satisfy AuthnContextSP requests assurance level the user does not have
urn:oasis:…:RequestDeniedRequest denied by policyAuth 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 CodeDescriptionCommon Fix
invalid_requestMissing or malformed parameterCheck that all required params are present and URL-encoded correctly
invalid_clientClient authentication failedVerify client_id is registered in Hawiyati admin console
invalid_grantAuthorization code invalid, expired, or already usedExchange the code immediately after redirect; codes are single-use
unauthorized_clientClient not permitted for this grant typeVerify the client's allowed grant types in admin console
unsupported_grant_typeGrant type not supportedHawiyati supports authorization_code and refresh_token only
invalid_scopeRequested scope not allowedVerify the scope is registered for the client; remove unsupported scopes
redirect_uri_mismatchRedirect URI not registeredAdd the exact redirect URI (including query string if any) to client config
code_challenge_failedPKCE verifier does not match challengeEnsure code_verifier is the original random string, not re-hashed
server_errorUnexpected IdP errorCheck Hawiyati application logs; report with request timestamp and client_id
temporarily_unavailableIdP temporarily down or overloadedImplement 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.

scimTypeHTTP StatusMeaning
invalidFilter400Filter expression syntax error or unsupported attribute
tooMany400Too many results — narrow the filter or use pagination
uniqueness409Attribute value must be unique — username or externalId already exists
mutability400Attempt to modify a read-only attribute (e.g., id, meta)
invalidSyntax400JSON body does not conform to SCIM schema
invalidPath400PATCH path references an attribute that does not exist
noTarget400PATCH filter matched no values
invalidValue400Attribute value is invalid (e.g., non-E.164 phone number)
invalidVers400ETag version mismatch in conditional update
sensitive403Attempt 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 / CapabilityStatusNotes
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 eq filters.

KYC / Biometrics

  • L3/L4 KYC frozen — The Strong and High Assurance workflows are implemented but held pending biometric partner approval. kyc_profiles.current_level will 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.
Production Blockers gRPC mTLS enforcement is a P0 item before production go-live. Do not deploy to production without addressing this.

Roadmap

The following capabilities are planned but not yet implemented. Timelines are indicative and subject to change.

CapabilityTarget HorizonNotes
SCIM Groups inboundNear-termNext minor release. Required for group-based access policies via SCIM provisioning.
Login lockout enforcementShipped 2026-06-16Available. Configurable via admin Settings.
gRPC mTLSNear-termRequired for production. Certificate provisioning and config underway.
KYC L3/L4 (biometric)Medium-termPending biometric partner integration approval and liveness vendor selection.
OIDC back-channel logoutShipped 2026-06-20Available. Configure backchannel_logout_uri on the SP registration.
AD / Kerberos connector28–36 monthsEnterprise moat item. Native Kerberos pass-through for domain-joined clients.
WS-Federation28–36 monthsLegacy .NET and SharePoint integration.
RADIUS28–36 monthsVPN and network access MFA.
SCIM outbound provisioning28–36 monthsPush identity events to downstream systems.
Connector catalog28–36 monthsPre-built SP connectors for common enterprise SaaS applications.
Backup automationNear-termScheduled PostgreSQL + Redis backup with verification and alerting.
Staying Current Monitor the Hawiyati release notes and docs/SESSION_STATE.md for updates to this roadmap. The feature matrix above is updated with each release.
HawiyatiDocumentation · v2026 · Spring Boot 3.5