DOC-5033 SAML guides

Author: cmilesb

content/operate/rc/security/access-control/saml-sso/saml-integration-auth0.md

@@ -175,16 +175,14 @@ Replace `ID` so it matches the `AssertionConsumerService` Location URL ID (the c
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-   A popup appears, explaining that, in order to test the SAML connection, that we need to login with credentials of a user defined in Auth0.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+   A popup appears, explaining that, in order to test the SAML connection, that we need to login with credentials of a user defined in Auth0. Select **Continue** to go to the Auth0 login screen.
 
 1. The Auth0 login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/auth0_saml_12.png" >}}
 
-1. If the test has succeeded, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-1. Enter your SAML email and select **Login**. 
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-You have successfully configured SAML as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}

content/operate/rc/security/access-control/saml-sso/saml-integration-aws-identity-center.md

@@ -138,18 +138,14 @@ The final step in our SAML integration with AWS IAM identity Center is to activa
 
    {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-  A logout notification screen displays, letting you know that you are redirected to AWS IAM Identity Center's login screen.
-
-   {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+  A logout notification screen displays, letting you know that you will be redirected to your identity provider. Select **Continue** to go to the AWS IAM Identity Center's login screen.
 
 1. Enter your AWS IAM Identity Center credentials.
 
    {{<image filename="images/rc/saml/aws_iam_identity_center_saml_18.png" >}}
 
-1. If everything is configured correctly, you should get a **SAML activation succeeded** message. From this point forward, users need to click **SSO** to sign in to the Redis Cloud console.
-
-   {{<image filename="images/rc/saml/aws_iam_identity_center_saml_19.png" >}}
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-  A message displays, stating that your local user is now converted to a SAML user. Select **Confirm**.
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured AWS IAM Identity Center as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}

content/operate/rc/security/access-control/saml-sso/saml-integration-azure-ad.md

@@ -163,23 +163,17 @@ Make sure the **Namespace** field is empty when modifying these claims.
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-1. A popup appears, explaining that you must log in with the credentials of a Microsoft Entra user to test the SAML connection.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+1. A popup appears, explaining that you must log in with the credentials of a Microsoft Entra user to test the SAML connection. Select **Continue** to go to the Microsoft login screen.
 
 1. The Microsoft login screen will appear. Enter the credentials and click **Sign In**.
 
     {{<image filename="images/rc/saml/ad_saml_19.png" >}}
 
-1. If the test has succeeded, you will see the following screen. Your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and click **Login**.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/ad_saml_21.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured SAML as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
 
 ## Claim conditions and user groups
 

content/operate/rc/security/access-control/saml-sso/saml-integration-google.md

@@ -163,10 +163,8 @@ A logout notification screen displays, letting you know that you are redirected
 
    {{<image filename="images/rc/saml/google_workspace_saml_18.png" >}}
 
-1. If everything is configured correctly, you should get a **SAML activation succeeded** message. From this point forward, users need to click **SSO** to log in to the Redis Cloud console.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-   {{<image filename="images/rc/saml/google_workspace_saml_19.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-A message displays, stating that your local user is now converted to a SAML user. Select **Confirm**.
-
-You have successfully configured Google Workspace as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}

content/operate/rc/security/access-control/saml-sso/saml-integration-okta-generic.md

@@ -253,24 +253,14 @@ To activate SAML, you must have a local user (or social sign-on user) with the *
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-    A popup appears, stating that to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+    A popup appears, stating that to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application. Select **Continue** to go to the Okta login screen.
 
 1. The Okta login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/okta_saml_app_int_14.png" >}}
 
-1. If the test succeeds, your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and click **Login**.
-
-    {{<image filename="images/rc/saml/okta_saml_app_int_15.png" >}}
-
-1. If only one user is defined in Redis Cloud console, you get a popup window where you select **Confirm** to convert the local user to a SAML user. Consider setting up one more local user other than a SAML user.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/okta_saml_app_int_16.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-1. You have successfully configured SAML as an identity provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}

content/operate/rc/security/access-control/saml-sso/saml-integration-okta-org2org.md

@@ -241,20 +241,14 @@ Replace `<ID>` so it matches the AssertionConsumerService Location URL ID (the c
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-   A popup appears, explaining that, to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application.
+   A popup appears, explaining that, to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application. Select **Continue** to go to the Okta login screen.
 
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
-
-1. The Okta log-in screen appears. Enter the credentials and select **Sign In**.
+1. The Okta login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/sm_saml_10.png" >}}
 
-1. If the test succeeds, the next screen appears. Your local account is now considered a SAML account. Going forward, to log in to Redis Cloud console, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and select **Login**
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/sm_saml_12.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-You have successfully configured SAML as an identity provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}

content/operate/rc/security/access-control/saml-sso/saml-integration-ping-identity.md

@@ -162,25 +162,19 @@ To activate SAML, you must have a local user (or social sign-on user) with the *
 
 1. Return to the Redis Cloud console and select **Activate**.
 
-    {{<image filename="images/rc/saml/ping_identity_saml_19.png" >}}
+    {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-1. A popup appears, explaining that to test the SAML connection, you need to log in with credentials of a user defined in Ping Federate.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+1. A popup appears, explaining that to test the SAML connection, you need to log in with credentials of a user defined in Ping Federate. Select **Continue** to go to the Ping Federate login screen.
 
 1. The Ping Federate login screen will appear. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/ping_identity_saml_20.png" >}}
 
-1. If the test has succeeded, you will see the following screen. Your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select the **Sign in with SSO** button.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. In the screen, enter your SAML email and select *Login*.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/ad_saml_21.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured SAML as an identity provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
 
 ## IdP-initiated SSO