What the product does.
WexaIdentity is an independent identity and access governance control plane. It builds on mature identity providers and helps teams review access requests, delegated administration, revocation outcomes and application connections.
Named local implementation scopes are complete. Licensed vendor, customer, operator and production acceptance remain open.
Product capabilities
Review access across applications
Keep application access, requests, reviews, delegated administration and lifecycle work visible in a central control plane. Scope work by tenant, company, site, application and environment.
- Application access requests and reviews
- Delegated administration and lifecycle work
- Scoped management views and reporting
Build on an established identity provider
The local product uses a mature Keycloak identity foundation; customer Entra/AD federation is assessed for the proposed environment. Connected applications retain their own business authorization. WexaIdentity is optional for other Wexa products.
- Mature identity-provider foundation
- Separate application business permissions
- Recorded revocation and access outcomes
Evaluate the relevant tasks.
Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.
- Select an application, company, site and environment.
- Review a sample access request and delegated approval.
- Follow a lifecycle or revocation result, including unresolved outcomes.
- Agree the identity provider, connector permissions and customer acceptance cases.
Workflow walkthroughs
Review one access lifecycle
Bring an application inventory and anonymized role examples. Keep passwords, tokens, directory exports and production identity data out of the enquiry.
- Select an application, company, site and environment.
- Review a sample access request and delegated approval.
- Follow a lifecycle or revocation result, including unresolved outcomes.
- Agree the identity provider, connector permissions and customer acceptance cases.
Prepare a useful support request.
Include the exact WexaIdentity package or preview, environment and workflow. Confirm whether the issue concerns a local evaluation or an accepted customer installation.
- Bring an application inventory and anonymized role examples. Keep passwords, tokens, directory exports and production identity data out of the enquiry.
- Describe expected behaviour, what happened and any steps already tried. Do not send passwords, tokens, private files or production records.
- Remaining acceptance scope: Licensed vendor and customer integration acceptance; Operator UAT and customer security/retention setup; Production deployment and custody acceptance.
Your questions, answered.
Must every Wexa product use WexaIdentity?
No. WexaIdentity is an independent product with optional integrations; it is not a mandatory shared runtime or database.
Does revocation instantly remove access everywhere?
That is not assumed. Identity-provider sessions, application sessions and tokens have distinct lifecycles; observed outcomes and remaining windows need to be verified.