Merge branch 'main' into 3pcd-adsso

Author: edunham

_source/_posts/2024-02-29-net-scim.md

@@ -1514,7 +1514,7 @@ In this step, you will create an app integration in Okta. Although there are sev
 
 Log in to your Okta Developer Account. Ensure you're in the Admin Console — when you're in the Admin Console, the URL will be "dev-youraccountid-admin.okta.com". In the sidebar, select **Applications** > **Applications**, and press the **Browse App Catalog** button. 
 
-Enter "**SCIM 2.0 Test App**" in the search box. Select the "**SCIM 2.0 Test App (OAuth Bearer Token)**", and press the **+ Add Integration** button to confirm creating an integration using "SCIM 2.0 Test App (Header Auth)". 
+Enter "**SCIM 2.0 Test App**" in the search box. Select the "**SCIM 2.0 Test App (OAuth Bearer Token)**", and press the **+ Add Integration** button to confirm creating an integration using "SCIM 2.0 Test App (Bearer Token)". 
 
 You'll then see configuration options. Leave the options under the **General Settings** tab and navigate to the **Sign-On Options** tab. Give the app a helpful name in the **Application label** field. For example, you can keep the default or change it to ".NET SCIM Server". Leave the **Automatically log in when a user lands on login page** checked, and click **Next**. 
 

_source/_posts/2024-02-29-third-party-cookies.md

@@ -49,7 +49,10 @@ If you're using a custom domain like `login.mycompany.com` in your sign-in widge
 
 If you have a self-hosted Sign-In Widget with `mycompany.okta.com` configured as the `baseUrl` or `issuer` in its settings, cookies will be issued for `okta.com` and will be first-party to `okta.com` but third-party to `mycompany.com`. 
 
-If you have a self-hosted Sign-In Widget and use [agentless Desktop Signele Sign-on](https://help.okta.com/en-us/content/topics/directory/ad-dsso-test.htm), follow the steps in [this Knowledge Base article](https://support.okta.com/help/s/article/third-party-cookies-utilized-by-the-sign-in-widget?language=en_US) to embed a Trial token script. 
+
+### Third-party cookie deprecation when using Agentless Desktop Single Sign-on
+
+If you have a Custom Domain or Self-Hosted Sign-in Widget deployment model and use Agentless Desktop Single Sign-on (ADSSO), follow the steps in the [Third Party Cookies Utilized by the Sign-in Widget](https://support.okta.com/help/s/article/third-party-cookies-utilized-by-the-sign-in-widget) Knowledge Base article to enable `CookiesAllowedforURLs` in Chrome browsers. 
 
 ### Third-party cookie deprecation affects "remember me" features
 
@@ -69,4 +72,5 @@ Here on the Okta Developer Blog, we'll keep you updated about how to mitigate ea
 
 * Learn more about [how blocking third-party cookies affects Okta environments](https://support.okta.com/help/s/article/FAQ-How-Blocking-Third-Party-Cookies-Can-Potentially-Impact-Your-Okta-Environment?language=en_US).
 * See the [Okta session cookies guide](https://developer.okta.com/docs/guides/session-cookie/main/) for more on how cookies are used.
-* [Use Chrome's feature flags](https://support.okta.com/help/s/article/deprecation-of-3rd-party-cookies-in-google-chrome?language=en_US) to test your login experience with third-party cookies disabled.  
+* [Use Chrome's feature flags](https://support.okta.com/help/s/article/deprecation-of-3rd-party-cookies-in-google-chrome?language=en_US) to test your login experience with third-party cookies disabled.
+* Read the [Third Party Cookies Utilized by the Sign-in Widget](https://support.okta.com/help/s/article/third-party-cookies-utilized-by-the-sign-in-widget) Knowledge Base article

_source/_posts/2024-03-12-stepup-authentication.md

@@ -50,9 +50,9 @@ npm ci
 
 Open the project up in your favorite IDE. Let's take a quick look at the project organization. The project has an Angular frontend and NestJS API backend housed in a [Lerna](https://lerna.js.org/) monorepo. If you are curious about how to recreate the project, check out the repo's README file. I'll include all the `npx` commands, CLI commands, and the manual steps used to create the project.
 
-You need an authentication configuration to serve the project. Let's do so now.
+You need to set up an authentication configuration to serve the project. Let's do so now.
 
-## Set up the Identity Provide to use OAuth 2.0 and OpenID Connect
+## Set up the Identity Provider to use OAuth 2.0 and OpenID Connect
 
 You'll use Okta to handle authentication and authorization in this project securely.