Skip to content

Commit 89fce84

Browse files
committed
Update Blog “okta-sso-integration-for-green-lake-and-aruba-central”
1 parent 60986d4 commit 89fce84

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
@@ -77,7 +77,7 @@ Provide a name for the Aruba GreenLake SSO service (Okta application)
7777

7878
![](/img/ws-image5.png)
7979

80-
The **hpe\__ccs\__attribute** always starts with `version_1#`. You must first configure the attributes for HPE GreenLake CSS, and then Central. To do so, enter the PCID for the account, followed by the HPE GreenLake application ID. This will always be **00000000-0000-0000-0000-000000000000**. Following this, enter the role name and **ALL\__SCOPES**. Next, enter in the Aruba Central information. Start with the **app cid**, followed by the role name (i.e. Aruba Central Administrator), and then **ALL\__SCOPES**.
80+
The **hpe\__ccs\__attribute** always starts with `version_1#`. You must first configure the attributes for HPE GreenLake CSS, and then Central. To do so, enter the PCID for the account, followed by the HPE GreenLake application ID. This will always be **00000000-0000-0000-0000-000000000000**. Following this, enter the role name and **ALL\_SCOPES**. Next, enter in the Aruba Central information. Start with the **app cid**, followed by the role name (i.e. Aruba Central Administrator), and then **ALL\_SCOPES**.
8181

8282
Example:
8383

0 commit comments

Comments
 (0)