You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Compared to 2.1, a major architectural refactoring is proposed, with the following objectives:

  1. introduce a new, flexible UI for web access (Weblogin), which will
    1. replace the existing login forms for Admin Console and Enduser UI
    2. adapt to the configured Access Management features, i.e.
      1. if a given deployment supports a certain SAML 2.0 IdP or OpenID Connect Provider, then the login form will adapt accordingly
      2. if a given deployment requires MFA, the login form will handle the flow
  2. introduce a new component (APIGW), which will provide API gateway features
  3. introduce a new component (Keymaster) with purpose of coordinating all the other components, centralizing common configuration required by all domains; this will allow to go beyond the current multi-tenancy approach which requires a pre-existing Master domain and the need to handle off-line each domain's configuration
  4. split the existing features set into three subsets, so that any given deployment will pick only what required:
    1. idrepo - everything needed to manage identities as a repository: mainly, CRUD operations on Users, Groups and Any Objects
    2. idm - the provisioning features required to propagate, push and pull identities back and forth to External Resources
    3. am - the authentication and authorization features - mostly to build on top of existing libraries

  • No labels