draft 3rd party cookies post #1488
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for okta-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
alisaduncan
reviewed
Feb 28, 2024
Co-authored-by: Alisa <[email protected]>
_source/_posts/2024-02-29-3pc.md
Outdated
|
|
||
| If your sign-in experience is hosted on the same top-level domain as your application, third-party cookie deprecation won't affect its behavior. | ||
|
|
||
| If the sign-in experience and app are on different top-level domains, third-party cookie deprecation will break its ability to introspect and extend sessions, because these features use cookies. Authentication will still be possible, and tokens will still be returned, becasue these features do not rely on cookies. |
There was a problem hiding this comment.
I think we should start this article with a specific definition of "session". Tokens can represent a session in the same way cookies do
By session, do we always mean cookie-based session?
There was a problem hiding this comment.
+1 ^^
Also, "becasue" -> "because"
rchild-okta
reviewed
Feb 28, 2024
_source/_posts/2024-02-29-3pc.md
Outdated
|
|
||
| If your sign-in experience is hosted on the same top-level domain as your application, third-party cookie deprecation won't affect its behavior. | ||
|
|
||
| If the sign-in experience and app are on different top-level domains, third-party cookie deprecation will break its ability to introspect and extend sessions, because these features use cookies. Authentication will still be possible, and tokens will still be returned, becasue these features do not rely on cookies. |
There was a problem hiding this comment.
+1 ^^
Also, "becasue" -> "because"
edunham
commented
Feb 29, 2024
Co-authored-by: Jared Perreault <[email protected]>
edunham
commented
Feb 29, 2024
alisaduncan
approved these changes
Feb 29, 2024
Co-authored-by: Semona Igama <[email protected]>
deepu105
pushed a commit
to indiepopart/okta-blog
that referenced
this pull request
Apr 18, 2024
Co-authored-by: Alisa <[email protected]> Co-authored-by: Jared Perreault <[email protected]> Co-authored-by: Semona Igama <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r?
Note that the linked Help Center docs are going live sometime during the review process; I'll double check that the link works before publishing.