Skip to content

Commit 376b03e

Browse files
committed
Update Blog “okta-sso-integration-for-green-lake-and-aruba-central”
1 parent c9a0ab0 commit 376b03e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/blog/okta-sso-integration-for-green-lake-and-aruba-central.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Provide a name for the Aruba GreenLake SSO service (Okta Application)
7070

7171
![](/img/ws-image5.png)
7272

73-
The ***hpe_ccs_attribute*** will always start with **version_1#**. First, we’ll configure the attributes for GreenLake CCS, then Central. First enter the PCID for the account, followed by the GreenLake application ID. This will always be **00000000-0000-0000-0000-000000000000**. Then followed by the role name and **ALL_SCOPES**. Next will be the Aruba Central info. Start with the **app cid**, then the role name (IE Aruba Central Administrator) then **ALL_SCOPES**.
73+
The **hpe\_ccs\_attribute** will always start with **version_1#**. First, we’ll configure the attributes for GreenLake CCS, then Central. First enter the PCID for the account, followed by the GreenLake application ID. This will always be **00000000-0000-0000-0000-000000000000**. Then followed by the role name and **ALL_SCOPES**. Next will be the Aruba Central info. Start with the **app cid**, then the role name (IE Aruba Central Administrator) then **ALL_SCOPES**.
7474

7575
Example: 
7676

0 commit comments

Comments
 (0)