Skip to content

Commit 1383632

Browse files
authored
Merge pull request #2193 from prabhum456/cms/prabhum456/hpe-dev-portal/blog/configuring-sso-for-hpe-greenlake-central-private-cloud-enterprise-and-hpe-greenlake-glcp-using-okta
Create Blog “configuring-sso-for-hpe-greenlake-central-private-cloud-enterprise-and-hpe-greenlake-glcp-using-okta”
2 parents bea23c9 + 9f1ff14 commit 1383632

14 files changed

+160
-0
lines changed
Lines changed: 160 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,160 @@
1+
---
2+
title: How to implement a single sign-on solution to authenticate users onto the
3+
HPE GreenLake edge-to-cloud platform
4+
date: 2023-11-29T12:41:00.306Z
5+
featuredBlog: false
6+
externalLink: ""
7+
author: Prabhu Murthy - Cloud Operations
8+
authorimage: /img/Avatar1.svg
9+
thumbnailimage: /img/hpe-greenlake-sso-page.jpg
10+
disable: false
11+
tags:
12+
- HPE GreenLake Private Cloud Enterprise application
13+
- HPE GreenLake edge-to-cloud platform
14+
- sso
15+
- okta
16+
- Active Directory
17+
- hpe-greenlake
18+
---
19+
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.
20+
21+
In this blog post, I will walk you through the process of configuring Okta Active Directory (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.
22+
23+
### Before starting
24+
25+
Please review the [HPE GreenLake](https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us&page=GUID-D7192971-EF71-4304-B51E-548E7954E644.html) User Guide to understand how the SAML framework works in the context of HPE GreenLake for Private Cloud Enterprise Services for the HPE GreenLake edge-to-cloud platform.
26+
27+
### Configure SSO/SAML applications in Okta
28+
29+
To configure application metadata in Okta, complete the following steps:
30+
31+
* Step 1: Create an Okta SAML application
32+
* Step 2: Configure Sign On settings
33+
* Step 3: Export the SAML 2.0 IdP metadata
34+
* Step 4: Configure the SAML connection in the HPE GreenLake edge-to-cloud platform
35+
36+
**Step 1: Create an Okta SAML application**
37+
38+
1. Log into the Okta administration console.
39+
2. Click **Applications > Create new app integration.** The Create a new app integration window opens.
40+
3. Select SAML 2.0 and click **Next**.
41+
42+
![](/img/ws-image0.png)
43+
44+
Provide a name for the SAML application which gets connected to the HPE GreenLake edge-to-cloud platform
45+
46+
![](/img/saml_app-okta.jpg)
47+
48+
**Step 2: How to configure single sign-on settings**
49+
50+
1. Enter the SAML information.
51+
52+
Under General:
53+
54+
**Single Sign on URL:** https://sso.common.cloud.hpe.com/sp/ACS.saml2
55+
56+
**Audience URI (SP Entity ID):** https://sso.common.cloud.hpe.com
57+
58+
**Name ID format EmailAddress**
59+
60+
**Application username Email**
61+
62+
**NameID = user.email**
63+
64+
**gl_first_name = user.FirstName**
65+
66+
**gl_last_name = user.LastName**
67+
68+
**hpe_ccs_attribute = (See Below)**
69+
70+
See here for IdP attribute details: [](https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us)<https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us&page=GUID-D7192971-EF71-4304-B51E-548E7954E644.html>
71+
72+
A new SAML attribute has been added “hpe_ccs_attribute” which tells HPE GreenLake edge-to-cloud platform and HPE GreenLake for Private Cloud Enterprise application the exact role/permissions for each user. The following describes how to format the attribute.
73+
74+
Format: {version}#{pcid}:{app id}:{role_name}:{ALL_SCOPES}
75+
76+
Note : At present HPE GreenLake for Private Cloud Enterprise application role should be excluded.
77+
78+
![](/img/hpe-greenlake-saml-attributes.jpg)
79+
80+
![](/img/workspace-pcid.jpg)
81+
82+
![](/img/glp_role_name.jpg)
83+
84+
The **hpe_ccs_attribute** always starts with version1#. You must first configure the attributes for HPE GreenLake edge-to-cloud platform and 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**.** 
85+
86+
Example:
87+
88+
version_1#7ede5c36b7b911edacf45a78eb8b07d1:00000000-0000-0000-0000-000000000000:Observer:ALL_SCOPES
89+
90+
![](/img/saml_settings.jpg)
91+
92+
2. Complete the setup.
93+
94+
![](/img/ws-image7.png)
95+
96+
Click Next and Select “Internal App”, then Finish.
97+
98+
**Step 3:** **Export the SAML 2.0 IdP metadata**
99+
100+
1. Click Next – Configure the single sign-on settings
101+
102+
You will find two options are available: **View Setup Instructions** which steps you through the SAML configuration and **Identity Provider metadata**, which will produce an XML file that can be loaded into HPE GreenLake edge-to-cloud platform application
103+
104+
Suggestion: Click **Identity Provider metadata** and save the XML data to a file.
105+
106+
![](/img/ws-image9.png)
107+
2. Click **Next**.
108+
3. Select **Internal app**, and click **Finish**.
109+
110+
##### **Step 3.1 : Access to the SAML application and HPE GreenLake edge-to-cloud platform is determined by assigning only those members or group to the SAML application.**
111+
112+
![](/img/customer-user-assignment-to-saml.jpg)
113+
114+
115+
116+
**Step 4:** **Configure the SAML connection in the HPE GreenLake edge-to-cloud platform**
117+
118+
1. Log into HPE GreenLake edge-to-cloud platform and click Menu > Manage > Authentication and Click Set Up SAML Connection.
119+
120+
*Before you can add a new SAML configuration, you must have at least **one** user account with that **domain** already enabled in HPE GreenLake edge-to-cloud platform. Also, you must be logged into HPE GreenLake edge-to-cloud platform with an account from that domain in order to enable SSO for it.*
121+
122+
![](/img/ws-image10.png)
123+
2. Type in the domain you want to enable SSO on:
124+
125+
![](/img/glp_domain.jpg)
126+
3. Input the metadata from the step above.
127+
128+
While HPE GreenLake edge-to-cloud platform does support entering this information manually, it's recommended that you simply upload the XML metadata that was downloaded in the previous step. To do so, Select Metadata File, selecting the XML file. Then, click Next.
129+
130+
![](/img/ws-image12.png)
131+
4. Enter the SAML attributes to match what was entered in Okta. Set the idle timeout value as well.
132+
133+
![](/img/config_setting_sso_appjpg.jpg)
134+
5. Then click **Next**.
135+
6. Create a recovery user so that, in the event SSO fails, an admin will still be able to access the HPE GreenLake edge-to-cloud platform.
136+
137+
![](/img/recovery_user.jpg)
138+
139+
Congratulations! SSO will now be enabled for HPE GreenLake edge-to-cloud platform as well as the HPE GreenLake for Private Cloud Enterprise application. Log out and on the HPE GreenLake edge-to-cloud platform home page, click **Sign in with SSO**.
140+
141+
**Testing and troubleshooting:**
142+
143+
On the HPE GreenLake edge-to-cloud platform home page, click **Sign In with SSO**.
144+
145+
![](/img/ws-image15.png)
146+
147+
![](/img/hpe-greenlake-sso-page.jpg)
148+
149+
Enter the SSO credentials. You will be redirected to Okta to authenticate. Once you successfully authenticate, you will be redirected back to HPE GreenLake edge-to-cloud platform. You can then click on the HPE GreenLake for Private Cloud Enterprise application and be given access based on the configured role/permissions.
150+
151+
**Additional notes:**
152+
153+
* There must be at least **one** verified user belonging to the **Domain** prior to configuration.
154+
* In order to configure SSO, you must be logged into the HPE GreenLake edge-to-cloud platform with a user from the domain.
155+
* SSO user access is determined by the “role_name” attribute included in the SAML hpe_ccs_attribute provided by the IdP.
156+
* For more troubleshooting: <https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us>
157+
* Customer users should be given access to SAML application.
158+
* After authentication when clicking the HPE GreenLake 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. 
159+
160+
I hope this blog post answers any questions you may have had in regards to how to configure single sign-on for HPE GreenLake for Private Cloud Enterprise on the HPE GreenLake edge-to-cloud 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.
26 KB
Loading
26.3 KB
Loading

static/img/customer_saml_app.jpg

61.8 KB
Loading

static/img/glp_domain.jpg

26.3 KB
Loading

static/img/glp_role_name.jpg

46.6 KB
Loading
141 KB
Loading

static/img/hpe-greenlake-sso-page.jpg

40.6 KB
Loading

static/img/recovery_user.jpg

26.1 KB
Loading

static/img/saml_app-okta.jpg

64 KB
Loading

0 commit comments

Comments
 (0)