Skip to content

Commit ce15f98

Browse files
authored
Merge pull request #6157 from Yasasr1/shared-user-impersonation
Add docs for shared user impersonation
2 parents 391ca5e + f5d3cdc commit ce15f98

4 files changed

Lines changed: 96 additions & 2 deletions

File tree

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{% include "../../../../includes/guides/organization-management/shared-user-impersonation.md" %}

en/asgardeo/mkdocs.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -650,8 +650,10 @@ nav:
650650
- Generate tokens for organization applications: guides/organization-management/generate-tokens-for-organization-apps.md
651651
- Manage organization users:
652652
- Onboard users to organizations: guides/organization-management/onboard-users.md
653-
- Share users across organizations: guides/organization-management/share-user-profiles.md
654-
- Allow shared users to login to organizations: guides/organization-management/shared-user-direct-login.md
653+
- Shared users:
654+
- Share users across organizations: guides/organization-management/share-user-profiles.md
655+
- Allow shared users to log in to organizations: guides/organization-management/shared-user-direct-login.md
656+
- Allow impersonation for shared users: guides/organization-management/shared-user-impersonation.md
655657
- Customize organizations:
656658
- Organization settings:
657659
- Organization settings: guides/organization-management/inheritance-in-organizations/index.md

en/includes/guides/authorization/user-impersonation/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,5 @@ You can start user impersonation in two ways:
1010
1. [Via Console]({{base_path}}/guides/authorization/user-impersonation/via-console)
1111

1212
2. [Via business application (advanced)]({{base_path}}/guides/authorization/user-impersonation/via-business-application)
13+
14+
If the impersonator is a shared user (a user whose profile is managed by a parent organization), see [Allow impersonation for shared users]({{base_path}}/guides/organization-management/shared-user-impersonation).
Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
# Allow impersonation for shared users
2+
3+
Shared users are users whose profiles are managed by a parent organization but [shared with child organizations]({{base_path}}/guides/organization-management/share-user-profiles/). This guide explains how to allow shared users to impersonate other users within those child organizations.
4+
5+
To allow shared users to perform impersonation, the login flow of the relevant application must be updated to include the **Shared User Identifier** authenticator as its first step. This lets {{ product_name }} resolve the shared user's resident profile before proceeding with the remaining authentication steps. Learn more about [allowing shared users to log in to organizations]({{base_path}}/guides/organization-management/shared-user-direct-login/).
6+
7+
## Prerequisites
8+
9+
- The impersonator's user profile must be [shared with the organization]({{base_path}}/guides/organization-management/share-user-profiles/) where impersonation will take place.
10+
11+
- The target organization must have user impersonation already configured. If not, follow the steps in one of the guides below before proceeding:
12+
- [User impersonation via Console]({{base_path}}/guides/authorization/user-impersonation/via-console/)
13+
- [User impersonation via business application]({{base_path}}/guides/authorization/user-impersonation/via-business-application/)
14+
15+
## Impersonate via the console
16+
17+
To enable shared user impersonation via the Console, update the Console application's login flow in the target organization. Add the **Shared User Identifier** authenticator as its first step.
18+
19+
### Update the console login flow
20+
21+
1. Sign in to the {{ product_name }} Console of the **target organization**.
22+
23+
2. Go to **Console Settings** and go to the **Login Flow** tab.
24+
25+
3. Add the **Shared User Identifier** as the first step of the login flow.
26+
27+
=== "Classic Editor"
28+
29+
1. In the first step, click **Add Authentication** and select **Shared User Identifier**.
30+
31+
!!! note
32+
Remove the **Username & Password** authenticator from the first step. The **Shared User Identifier** must be the only authenticator in the first step.
33+
34+
2. Add a second authentication step by clicking the **+** icon and add your preferred authenticators (such as **Username & Password** or a passwordless option) to this step.
35+
36+
=== "Visual Editor"
37+
38+
1. Switch to the **Visual Editor** tab.
39+
40+
2. In the first step, click **+ Add Sign In Option** and select **Shared User Identifier**.
41+
42+
!!! note
43+
Remove the **Username & Password** authenticator from the first step. The **Shared User Identifier** must be the only authenticator in the first step.
44+
45+
3. Add a second authentication step by clicking the **+** icon and add your preferred authenticators to this step.
46+
47+
4. Click **Update** to save your changes.
48+
49+
Once configured, when a shared user logs in to the Console they will be prompted for their identifier in the first step. {{ product_name }} resolves the resident profile and then engages the authenticators in the second step to complete login.
50+
51+
The shared user can then follow the [standard Console impersonation steps]({{base_path}}/guides/authorization/user-impersonation/via-console/##impersonate-users-in-an-organization) to impersonate users within the organization.
52+
53+
## Impersonate via a business application
54+
55+
For a shared user to impersonate another user through a business application, add the **Shared User Identifier** authenticator as the first step of that application's login flow.
56+
57+
### Update the application login flow
58+
59+
1. Sign in to the {{ product_name }} Console of the **target organization**.
60+
61+
2. Go to **Applications** and select the application that the shared user will use for impersonation.
62+
63+
3. Go to the application's **Login Flow** tab.
64+
65+
4. Add the **Shared User Identifier** as the first step of the login flow.
66+
67+
=== "Classic Editor"
68+
69+
1. In the first step, click **Add Authentication** and select **Shared User Identifier**.
70+
71+
!!! note
72+
Remove the **Username & Password** authenticator from the first step. The **Shared User Identifier** must be the only authenticator in the first step.
73+
74+
2. Add a second authentication step by clicking the **+** icon and add your preferred authenticators (such as **Username & Password** or a passwordless option) to this step.
75+
76+
=== "Visual Editor"
77+
78+
1. Switch to the **Visual Editor** tab.
79+
80+
2. In the first step, click **+ Add Sign In Option** and select **Shared User Identifier**.
81+
82+
!!! note
83+
Remove the **Username & Password** authenticator from the first step. The **Shared User Identifier** must be the only authenticator in the first step.
84+
85+
3. Add a second authentication step by clicking the **+** icon and add your preferred authenticators to this step.
86+
87+
5. Click **Update** to save your changes.
88+
89+
Once configured, shared users can follow the [standard business application impersonation steps]({{base_path}}/guides/authorization/user-impersonation/via-business-application/#step-3-get-tokens-for-user-impersonation) to get a subject token and exchange it for an impersonated access token.

0 commit comments

Comments
 (0)