Skip to content

Commit cc4f351

Browse files
committed
Update Blog “configuring-sso-for-hpe-greenlake-central-private-cloud-enterprise-and-hpe-greenlake-glcp-using-okta”
1 parent 9cf3005 commit cc4f351

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/blog/configuring-sso-for-hpe-greenlake-central-private-cloud-enterprise-and-hpe-greenlake-glcp-using-okta.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Provide a name for the SAML application which gets connected to the HPE GreenLak
7979

8080
A new SAML attribute has been added “hpe\_ccs\_attribute” which tells HPE GreenLake platform and HPE GreenLake for Private Cloud Enterprise application the exact role/permissions for each user. The following describes how to format the attribute.
8181

82-
Format: {version}#{pcid}:{app id}:{role_name}:{ALL\_SCOPES}
82+
`Format: {version}#{pcid}:{app id}:{role_name}:{ALL_SCOPES}`
8383

8484
Note : At present HPE GreenLake for Private Cloud Enterprise application role should be excluded.
8585

@@ -93,7 +93,7 @@ The **hpe\_ccs\_attribute** always starts with version1#. You must first confi
9393

9494
Example:
9595

96-
version_1\#7ede5c36b7b911edacf45a78eb8b07d1:00000000-0000-0000-0000-000000000000:Observer:ALL\_SCOPES
96+
`version_1\#7ede5c36b7b911edacf45a78eb8b07d1:00000000-0000-0000-0000-000000000000:Observer:ALL_SCOPES`
9797

9898
![](/img/saml_settings.jpg)
9999

0 commit comments

Comments
 (0)