Update Blog “okta-sso-integration-for-green-lake-and-aruba-central”

Author: WifiGuyWill

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

@@ -41,7 +41,7 @@ Provide a name for the Aruba GreenLake SSO service (Okta application)
 
 ![](/img/ws-image1.png)
 
-**Step 2: Configure Single Sign On settings**
+**Step 2: How to configure Single Sign On settings**
 
 1. Enter the SAML information.
 
@@ -65,7 +65,7 @@ Provide a name for the Aruba GreenLake SSO service (Okta application)
 
    See here for IdP attribute details: <https://support.hpe.com/hpesc/public/docDisplay?docId=a00120892en_us>
 
-   One of the additional features added as part of the GreenLake platform is Role Based Access Controls (RBAC) for Aruba Central and all other apps in GLCP. A new SAML attribute has been added “hpe_ccs_attribute” which tells GreenLake and Central the exact role/permissions for each user. The following describes how to format the attribute.
+   As part of the HPE GreenLake cloud platform integration, one of the additional features that was added is the Role Based Access Controls for Aruba Central and all other apps on the platform. A new SAML attribute has been added “hpe\_ccs\_attribute” which tells GreenLake and Central the exact role/permissions for each user. The following describes how to format the attribute.
 
 ![](/img/ws-image2.png)
 
@@ -75,15 +75,15 @@ Provide a name for the Aruba GreenLake SSO service (Okta application)
 
 ![](/img/ws-image5.png)
 
-The **hpe\_ccs\_attribute** will always start with **version_1#**. First, we’ll configure the attributes for GreenLake CCS, then Central. First enter the PCID for the account, followed by the GreenLake application ID. This will always be **00000000-0000-0000-0000-000000000000**. Then followed by the role name and **ALL_SCOPES**. Next will be the Aruba Central info. Start with the **app cid**, then the role name (IE Aruba Central Administrator) then **ALL_SCOPES**.
+The **hpe\_ccs\_attribute** always starts with version_1#. You must first configure the attributes for HPE GreenLake CSS, and then Central. 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**. Next, enter in the Aruba Central information. Start with the **app cid**, followed by the role name (i.e. Aruba Central Administrator), and then **ALL_SCOPES**.
 
 Example:
 
 **version_1#5b0ec0e8c4f422eca232ba72799953ac:00000000-0000-0000-0000-000000000000:Account Administrator:ALL_SCOPES:683da368-66cb-4ee7-90a9-ec1964768092:**
 
 **Aruba Central Administrator:ALL_SCOPES**
 
-If you want to add additional GreenLake applications or if you have multiple Aruba Central accounts, you can add them as well. Just follow the same syntax as before. Once you have the attribute defined, enter it into the SAML attribute statement in Okta as shown below.
+If you want to add additional HPE GreenLake applications, or if you have multiple Aruba Central accounts, you can add them as well. Just follow the same syntax as before. Once you have the attribute defined, enter it into the SAML attribute statement in Okta as shown below.
 
 ![](/img/ws-image6.png)
 
@@ -97,27 +97,27 @@ Click Next and Select “Internal App” then Finish
 
 1. Click Next – Configure the Sign On settings
 
-   Two options available: **View Setup Instructions** which steps through the SAML config or **Identity Provider metadata** will produce an XML that can be loaded into Aruba Central.
+   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 Aruba Central.
 
    Suggestion: Click **Identity Provider metadata** and save the XML data to a file.
 
    ![](/img/ws-image9.png)
 2. Click Next
-3. Select Internal app and Click Finish
+3. Select Internal app, and Click Finish
 
-**Step 4: Create SAML Authorization Profile in GreenLake Cloud Platform**
+**Step 4: Create SAML Authorization Profile in HPE GreenLake Cloud Platform**
 
-1. Log into GreenLake and click Menu > Manage > Authentication and Click Set Up SAML Connection.
+1. Log into HPE GreenLake and click Menu > Manage > Authentication and Click Set Up SAML Connection.
 
-   *Before you can add a new SAML configuration, you must have at least one user account with that domain already enabled in GreenLake. Also, you must be logged into GreenLake with an account from that domain in order to enable SSO for that domain.*
+   *Before you can add a new SAML configuration, you must have at least one user account with that domain already enabled in HPE GreenLake. Also, you must be logged into GreenLake with an account from that domain in order to enable SSO for it.*
 
    ![](/img/ws-image10.png)
 2. Type in the domain you want to enable SSO on:
 
    ![](/img/ws-image11.png)
-3. Input the metadata from the above step
+3. Input the metadata from the step above.
 
-   While GreenLake does support manually entering this info, it’s recommended to simply upload the XML metadata that was downloaded in the previous step. Select Metadata File and select the XML. Then click Next.
+   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.
 
    ![](/img/ws-image12.png)
 4. Enter the SAML attributes to match what was entered in Okta and set the idle timeout value as well.