OIDC sso topic updates (#376)

* note + image update * note fix * image resize * note update * image size + note * removing cwp note * review feedback
hlxsites · Feb 5, 2024 · 6ed279e · 6ed279e
1 parent 5b741aa
commit 6ed279e
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 8 deletions.
diff --git a/...en/enterprise-edition/content-collections/_graphics/administration/oidc-sso.png b/...en/enterprise-edition/content-collections/_graphics/administration/oidc-sso.png
diff --git a/docs/en/enterprise-edition/content-collections/_graphics/administration/oidc.png b/docs/en/enterprise-edition/content-collections/_graphics/administration/oidc.png
diff --git a/...ration-on-prisma-cloud/get-started-with-oidc-sso/get-started-with-oidc-sso.adoc b/...ration-on-prisma-cloud/get-started-with-oidc-sso/get-started-with-oidc-sso.adoc
@@ -2,13 +2,18 @@
 [.task]
 == Get Started with OIDC SSO
 
-Prisma Cloud offers a Service Provider initiated SSO capability. Leveraging OpenID Connect https://openid.net/developers/how-connect-works/[OpenID Connect (OIDC)], this option enables Prisma Cloud System Administrators to allow users to sign in to Prisma Cloud with their Identity Provider (IdP) credentials using the *Sign in via SSO* button on the login page. Learn more about setting up SP-initiated SSO below.
+Prisma Cloud offers a Service Provider (SP) initiated SSO capability. Leveraging OpenID Connect https://openid.net/developers/how-connect-works/[OpenID Connect (OIDC)], this option enables Prisma Cloud System Administrators to allow users to sign in to Prisma Cloud with their Identity Provider (IdP) credentials using the *Sign in via SSO* option on the login page. Learn more about setting up SP-initiated SSO below.
+
+[CAUTION]
+====
+To avoid account lockout while making configuration changes, enable administrative users with both local authentication credentials on Prisma Cloud and SSO access. Ensure that each administrator has activated their Palo Alto Networks Customer Support Portal (CSP) account using the Welcome to Palo Alto Networks Support email and set a password to access the portal.
+====
 
 image::administration/oidc-sso.png[]
 
-[CAUTION]
+[NOTE]
 ====
-To avoid account lockout while making configuration changes, you may enable administrative users with both local authentication credentials on Prisma Cloud and SSO access. Ensure that each administrator has activated their Palo Alto Networks Customer Support Portal (CSP) account using the Welcome to Palo Alto Networks Support email and set a password to access the portal.
+The Sign in via SSO button enables login with a configured OIDC SSO provider. To sign in using third party Security Assertion Markup Language (SAML) SSO, use the Identity Provider defined for the SAML integration with the Prisma Cloud tenant.
 ====
 
 Complete the steps below on the Prisma Cloud console and your IdP to set up OIDC:
@@ -20,7 +25,7 @@ Complete the steps below on the Prisma Cloud console and your IdP to set up OIDC
 image::administration/oidc.png[]
 .. Copy the *Audience URI* value. This is a read-only field in the format that uniquely identifies your instance of Prisma Cloud. This value is required to configure OIDC on your IdP.
 +
-NOTE: The Prisma ID of a tenant is displayed adjacent the OIDC configuration so that it can be shared with users that may have  access to multiple tenants. If you have access to multiple tenants on a stack you will be required to enter the Prisma ID of the tenant you are logging into. 
+tt:[NOTE:] The Prisma ID of a tenant is displayed adjacent the OIDC configuration so that it can be shared with users that may have  access to multiple tenants. If you have access to multiple tenants on a stack you will be required to enter the Prisma ID of the tenant you are logging into. 
 
 . Complete the setup on the IdP.
 .. Review the workflow for your IdP.

diff --git a/...nnect/connect-cloud-accounts/onboard-aws/update-onboarded-aws-accnt-to-org.adoc b/...nnect/connect-cloud-accounts/onboard-aws/update-onboarded-aws-accnt-to-org.adoc
@@ -38,7 +38,8 @@ You can enter the same *Account Name* as the one you had entered while onboardin
 After successfully onboarding the account, you will see it onboarded as an *Organization* on the *Cloud Accounts* page.
 //+image::connect/aws-accnt-to-org-0-6.png[]
 
-[NOTE]
-====
-Updating from an individual account to an *Organization* is not supported for *Agentless* functions. If you previously onboarded a single account and now wish to switch to an *Organization* you will need to delete the single account on Prisma Cloud before proceeding with creating an *Organization*. 
-====
+//[NOTE]
+//====
+//Updating from an individual account to an *Organization* is not supported for *Agentless* functions. If you previously onboarded a single account and now wish to switch to an *Organization* you will need to delete the single account on Prisma Cloud before proceeding with creating an *Organization*. 
+//====
+//commenting out note till we reach consensus on CWP-54320