As discussed mentioned in a prior modulediscussion, Account Stores are external directories or “applications aka apps” containing their own accounts and groups. In EmpowerID, there exists an AccountStore table and a ProtectedApplicationResources table for storing EmpowerID’s definition of applications. The relationship between these two entities can be confusing, so we’ll attempt to clarify the concept here.
...
In the internal directory scenario described above, when onboarding these applications in EmpowerID, the admin would select the Account Store defined for the app's internal directory. This lets EmpowerID know which Account Store contains the accounts and groups that can access the application. However, in our eternal directory scenario, the admin would onboard multiple applications where EmpowerID would be selected as the Account Store for the application. In this scenario, where many applications in EmpowerID share the same Account Store for their security, the application owner can select specific groups in any Account Store to link as granting access to that application.
...
.
...
Key Components Related to an EmpowerID Application
...
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
...
| Tip |
|---|
Key Takeaways:
|
| Info |
|---|
Related Docs Topics: |
...