v3.1.0 - Refactor: HttpOnly cookies #90
Merged
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.
Changes & Additions
OAuth2, Local Scheme & Inheritances
The
tokenandrefreshTokenproperty for the scheme includes anhttpOnlyproperty that will enable the httpOnly flag on the token and fresh token cookies. This option is disabled by default. (In a later version it will be enabled by default)All schemes (custom & built-in) will use a
serverHandlerif ssr is available to manage the creation of httpOnly cookies and authorization.A reset
serverHandlerhas been added to handle the deletion of the httpOnly cookies when logging out/using the reset functionnuxt-alt/http
event.$httpnitro plugin has been added which works similar to whatevent.$fetchdoes, the difference being that it inherits the options of the http module.$httpin nitro would lead to a fetch error.