Versions Compared

Old Version 9

changes.mady.by.user Patrick Parker

Saved on

compared with

New Version 10

changes.mady.by.user Patrick Parker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Protected Application Resources like pages, controls, APIs

  • SSO Connections (SAML, OpenID Connect, etc.)

  • OAuth Scopes configuration

  • Multi-Factor Authentication settings

  • PBAC rights and roles

  • Groups and roles that should be requestable for this app in the IT Shop

Info

Key Takeaways:

  1. Multiple applications can be configured to useMost applications are a one to one with an Account Store that represents their internal directory.

  2. Applications that share an Account Store would select to use EmpowerID as the Account Store and then link the specific groups to which they wish to grant access to their application.

  3. An application object is not automatically created for each Account Store in EmpowerID.

  4. Any application configured for SSO requires an application object in EmpowerID.

  5. The component for applications and their subcomponents is named ProtectedApplicationResource.

  6. During application onboarding selecting to create a Tracking Only Account Store will create a “logical” Account Store in EmpowerID for access requests and tracking that is not inventoried or managed.