Skip to content

Commit d111dfd

Browse files
edunhamalisaduncan
andauthored
Apply suggestions from code review
Co-authored-by: Alisa <7586237+alisaduncan@users.noreply.github.com>
1 parent 3e556cc commit d111dfd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_source/_posts/2024-02-29-3pc.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: blog_post
3-
title: "The end of Third Party Cookies"
3+
title: "The End of Third-Party Cookies"
44
author: edunham
55
by: advocate
66
communities: [devops,security,mobile,.net,java,javascript,go,php,python,ruby]
@@ -31,7 +31,7 @@ Most code using Okta doesn't use 3rd party cookies, and won't be affected by the
3131

3232
Okta uses cookies to let applications introspect and extend user sessions. Cookies aren't required for basic login functionality.
3333

34-
### Web Applications that rely on the Okta session for user context.
34+
### Web applications that rely on the Okta session for user context.
3535

3636
If an application hosted on your domain (`mycompanyapp.com`) redirects to your Okta subdomain (`mycompany.okta.com`) for login and then returns users to your own domain, 3rd party cookie restrictions will limit how your app can introspect or extend the Okta session.
3737

0 commit comments

Comments
 (0)