Skip to content

Commit 050ae4d

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

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -35,15 +35,15 @@ Please review the [HPE GreenLake](https://support.hpe.com/hpesc/public/docDispl
3535

3636
**Step 1: Create an Okta SAML application**
3737

38-
1. Log in to the Okta administration console.
38+
1. Log into the Okta administration console.
3939
2. Click **Applications > Create new app integration.** The Create a new app integration window opens.
4040
3. Select SAML 2.0 and click **Next**.
4141

4242
![](/img/ws-image0.png)
4343

4444
Provide a name for the SAML application which gets connected to the HPE GreenLake edge-to-cloud platform
4545

46-
![](/img/customer_saml_app.jpg)
46+
![](/img/saml_app-okta.jpg)
4747

4848
**Step 2: How to configure single sign-on settings**
4949

@@ -67,15 +67,15 @@ Provide a name for the SAML application which gets connected to the HPE GreenLak
6767

6868
**hpe_ccs_attribute = (See Below)**
6969

70-
See here for IdP attribute details: <https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us>
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>
7171

7272
A new SAML attribute has been added “hpe_ccs_attribute” which tells HPE GreenLake edge-to-cloud platform and HPE GreenLake Private Cloud Enterprise application the exact role/permissions for each user. The following describes how to format the attribute.
7373

7474
Format: {version}#{pcid}:{app id}:{role_name}:{ALL_SCOPES}
7575

76+
Note : At present HPE GreenLake Private Cloud Enterprise application role should be excluded
7677

77-
78-
![](/img/hpe-greenlake-saml-attributes.jpg)
78+
![](/img/saml_app-okta2.jpg)
7979

8080
![](/img/workspace-pcid.jpg)
8181

@@ -97,15 +97,15 @@ Click Next and Select “Internal App”, then Finish.
9797

9898
**Step 3:** **Export the SAML 2.0 IdP metadata**
9999

100-
1. Click Next – Configure the Sign On settings
100+
1. Click Next – Configure the single sign-on settings
101101

102102
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
103103

104104
Suggestion: Click **Identity Provider metadata** and save the XML data to a file.
105105

106106
![](/img/ws-image9.png)
107-
2. Click Next.
108-
3. Select Internal app, and Click Finish.
107+
2. Click **Next**.
108+
3. Select **Internal app**, and click **Finish**.
109109

110110
##### **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.**
111111

@@ -131,8 +131,8 @@ Click Next and Select “Internal App”, then Finish.
131131
4. Enter the SAML attributes to match what was entered in Okta. Set the idle timeout value as well.
132132

133133
![](/img/config_setting_sso_appjpg.jpg)
134-
5. Then click Next.
135-
6. Create a recover user so that, in the event SSO fails, an admin will still be able to access the HPE GreenLake edge-to-cloud platform.
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.
136136

137137
![](/img/recovery_user.jpg)
138138

static/img/saml_app-okta.jpg

64 KB
Loading

static/img/saml_app-okta2.jpg

57.8 KB
Loading

0 commit comments

Comments
 (0)