Skip to content

Commit a24fc1e

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

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,15 @@ authorimage: /img/Avatar1.svg
99
thumbnailimage: /img/hpe-greenlake-sso-page.jpg
1010
disable: false
1111
tags:
12-
- HPE Greenlake Central (Private Cloud Enterprise)
13-
- hpe-greenlake-cloud-platform
12+
- HPE GreenLake Private Cloud Enterprise application
13+
- HPE GreenLake edge-to-cloud platform
1414
- sso
1515
- okta
16-
- Private Cloud Enterprise
16+
- Active Directory
1717
- hpe-greenlake
1818
---
19+
20+
1921
Enterprises looking to use HPE GreenLake for Private Cloud Enterprise can benefit from the use of SSO, as it has been integrated onto the HPE GreenLake edge-to-cloud platform, which supports single sign-on
2022

2123
In this blog post, I will walk you through the process of configuring Okta AD to authenticate users into the HPE GreenLake for Private Cloud Enterprise application on the HPE GreenLake platform using SAML Identity Provider (IdP) for single sign-on.
@@ -154,9 +156,7 @@ Enter the SSO credentials. You will be redirected to Okta to authenticate. Once
154156
* In order to configure SSO, you must be logged into the HPE GreenLake edge-to-cloud platform with a user from the domain.
155157
* SSO user access is determined by the “role_name” attribute included in the SAML hpe_ccs_attribute provided by the IdP.
156158
* For more troubleshooting: <https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us>
159+
* Customer users should be given access to SAML application.
160+
* After authentication when clicking the HPE GreenLake edge-to-cloud platform for Private Cloud Enterprise application**,** if it leads to the below error, it will take 1 hr to sync. If it does not do so within that time period, the customer should contact their HPE administrator. 
157161

158-
* Customer users should be given access to SAML application.
159-
160-
After authentication when clicking the HPE GreenLake edge-to-cloud platform for Private Cloud Enterprise application**,** if it leads to the below error, it will take 1 hr to sync. If it does not do so within that time period, the customer should contact their HPE administrator. 
161-
162-
![](/img/user_sync.jpg)
162+
I hope this blog post answers any questions you may have had in regards to how to configure single sign-on for HPE GreenLake Private Cloud Enterprise on the HPE GreenLake platform using Okta Active Directory. Please return back to the [HPE Developer blog](https://developer.hpe.com/blog) for more tips and tricks on working with the HPE GreenLake edge-to-cloud platform. If you have any further questions, please feel free to reach out to us via the #glc-support Slack channel.

0 commit comments

Comments
 (0)