WexaIdentity / Identity & access governance
Understand who has access. Review how it changes.
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.
Evaluation scope and delivery confirmed with the team
Discuss an evaluationReview product scope, licensing and implementation during evaluation.
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 connector behaviour before activation
Local ERP/CRM connector and provisioning scopes have separate evidence. A configured connection or local fixture is not licensed vendor or customer acceptance. Review direction, ownership, conflict handling and current permissions before allowing changes. Global immediate revocation is not assumed.
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.