Skip to content

Commit 7fb9a06

Browse files
Update content/blog/bulk-onboarding-of-users-in-hpe-greenlake-edge-to-cloud-platform.md
Co-authored-by: joe-boyle24 <[email protected]>
1 parent a56cd4b commit 7fb9a06

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/blog/bulk-onboarding-of-users-in-hpe-greenlake-edge-to-cloud-platform.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In this blog post, I will focus on one specific API call, part of Identity Manag
3131

3232
## Providing the right data to the script
3333

34-
Before writing any code, it’s important to understand what data is required to invite a user. According to the [API reference](https://developer.greenlake.hpe.com/docs/greenlake/services/iam/workspaces/public/openapi/workspaces-v1/operation/invite_user_to_account_identity_v1_users_post/), one simply needs the email address of the invited user. That’s easy! In the documentation, you can also see that there is no way to select a workspace to invite the user to. The reason for this is that the API credentials used to make the call is workspace specific, so it implicitly provides the workspace to which the user will be invited to. This means that one needs to collect API access credentials for every workspace that to the users are added to. For the script I am writing here, in a Workspace tab, I have stored the Client Id corresponding to API Access of a given Workspace. Because I don’t want to save Client Secrets, I will prompt for them and store them in memory.
34+
Before writing any code, it’s important to understand what data is required to invite a user. You only need the email address of the invited user- that’s easy! In the [API reference](https://developer.greenlake.hpe.com/docs/greenlake/services/iam/workspaces/public/openapi/workspaces-v1/operation/invite_user_to_account_identity_v1_users_post/), you'll also see that there is no way to select a workspace to invite the user to. The reason for this is that the API credentials used to make the call is workspace specific, so it implicitly provides the workspace to which the user will be invited to. This means that you need to collect API access credentials for every workspace that you're adding users to. For the script I am writing here, in the Workspaces tab, I have stored the Client Id corresponding to API Access of a given Workspace. Because I don’t want to save Client Secrets, I will prompt for them and store them in memory.
3535

3636
So, my Excel file contains the following 2 sheets:
3737

0 commit comments

Comments
 (0)