Skip to content

Commit 86264d4

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

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

content/blog/okta-sso-integration-for-green-lake-and-aruba-central.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -120,31 +120,31 @@ Click Next and Select “Internal App” then Finish
120120
While HPE GreenLake 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.
121121

122122
![](/img/ws-image12.png)
123-
4. Enter the SAML attributes to match what was entered in Okta and set the idle timeout value as well.
123+
4. Enter the SAML attributes to match what was entered in Okta. Set the idle timeout value as well.
124124

125125
![](/img/ws-image13.png)
126126
5. Then click Next.
127-
6. Create a recovery user in the event SSO fails, an admin will still be able to access GreenLake.
127+
6. Create a recover user so that, in the event SSO fails, an admin will still be able to access the HPE GreenLake portal.
128128

129129
![](/img/ws-image14.png)
130130

131-
Congratulations SSO will now be enabled for GreenLake as well as the Aruba Central application. Log out and on the GreenLake home page, click Sign in with SSO.
131+
Congratulations! SSO will now be enabled for HPE GreenLake as well as the Aruba Central application. Log out and on the HPE GreenLake home page, click Sign in with SSO.
132132

133-
**Testing and Troubleshooting:**
133+
**Testing and troubleshooting:**
134134

135-
On the GreenLake Cloud Platform home page, Click Sign in with SSO.
135+
On the HPE GreenLake Cloud Platform home page, click Sign In with SSO.
136136

137137
![](/img/ws-image15.png)
138138

139139
![](/img/ws-image16.png)
140140

141-
Enter the SSO credentials and you will be redirected to Okta to authenticate. Once you successfully authenticate, you will be redirected back to GreenLake. You can then click on the Aruba Central application and given access based on the configured role/permissions.
141+
Enter the SSO credentials. You will be redirected to Okta to authenticate. Once you successfully authenticate, you will be redirected back to HPE GreenLake. You can then click on the Aruba Central application and be given access based on the configured role/permissions.
142142

143-
**Additional Notes:**
143+
**Additional notes:**
144144

145145
* There must be at least **one** verified user belonging to the **Domain** prior to configuration.
146-
* In order to configure SSO, you must be logged into GreenLake with a user from the domain.
146+
* In order to configure SSO, you must be logged into HPE GreenLake with a user from the domain.
147147
* SSO user access is determined by the “role_name” attribute included in the SAML hpe_ccs_attribute provided by the IdP.
148-
* SSO users can initiate a Single Sign On request by trying to log in to Aruba Central (SP-initiated login).
148+
* SSO users can initiate a Single Sign On request by trying to log into Aruba Central (SP-initiated login).
149149
* For more troubleshooting: <https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us>
150150

0 commit comments

Comments
 (0)