-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add example for handling authentication with useCookie in Nuxt docs #29538
base: main
Are you sure you want to change the base?
Conversation
Run & review this pull request in StackBlitz Codeflow. |
WalkthroughThe documentation for the Changes
Possibly related PRs
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
🧹 Outside diff range and nitpick comments (1)
docs/3.api/2.composables/use-cookie.md (1)
239-266
: Add usage examples to the documentation.The plugin provides authentication methods but doesn't show how to use them in components or pages.
Consider adding an example of how to use these methods:
<script setup lang="ts"> const { $loginUser, $logout } = useNuxtApp() async function handleLogin(credentials) { try { const user = await $fetch('/api/login', { method: 'POST', body: credentials }) await $loginUser(user) await navigateTo('/dashboard') } catch (error) { // Handle login error } } async function handleLogout() { await $logout() } </script>
```ts [plugins/auth.ts] | ||
export default defineNuxtPlugin(() => { | ||
const nuxtApp = useNuxtApp() | ||
const authStore = useAuthStore() | ||
const accessToken = useCookie('accessToken', { | ||
sameSite: 'strict', | ||
}) | ||
|
||
return { | ||
provide: { | ||
getAccessToken() { | ||
return accessToken.value | ||
}, | ||
setAccessToken(accessToken: string) { | ||
accessToken.value = accessToken | ||
}, | ||
loginUser(user: User) { | ||
nuxtApp.$setAccessToken(user.accessToken) | ||
authStore.setUser(user) | ||
}, | ||
logout() { | ||
nuxtApp.$setAccessToken('') | ||
authStore.logout() | ||
}, | ||
}, | ||
} | ||
}) | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Add TypeScript types and improve error handling.
The plugin implementation needs better type safety and error handling:
+interface User {
+ accessToken: string;
+ // add other user properties
+}
+
export default defineNuxtPlugin(() => {
const nuxtApp = useNuxtApp()
const authStore = useAuthStore()
const accessToken = useCookie('accessToken', {
sameSite: 'strict',
+ httpOnly: true,
+ secure: process.env.NODE_ENV === 'production',
})
return {
provide: {
- getAccessToken() {
+ getAccessToken(): string | null {
return accessToken.value
},
- setAccessToken(accessToken: string) {
+ setAccessToken(token: string): void {
try {
- accessToken.value = accessToken
+ accessToken.value = token
+ } catch (error) {
+ console.error('Failed to set access token:', error)
+ throw new Error('Authentication failed')
+ }
},
- loginUser(user: User) {
+ async loginUser(user: User): Promise<void> {
+ if (!user?.accessToken) {
+ throw new Error('Invalid user data')
+ }
nuxtApp.$setAccessToken(user.accessToken)
authStore.setUser(user)
},
- logout() {
+ async logout(): Promise<void> {
nuxtApp.$setAccessToken('')
+ accessToken.value = null
authStore.logout()
+ await navigateTo('/login') // Redirect to login page
},
},
}
})
Also, consider adding JSDoc comments to document the usage of these methods:
/**
* Returns the current access token from the cookie
* @returns {string | null} The access token or null if not set
*/
getAccessToken(): string | null
/**
* Sets the access token in the cookie
* @param {string} token - The access token to store
* @throws {Error} If the token cannot be set
*/
setAccessToken(token: string): void
|
||
## Handling Authentication with Cookies | ||
|
||
You can manage authentication tokens using cookies like this: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Enhance the authentication section with security considerations and best practices.
The introduction should provide more context and security considerations for handling authentication tokens with cookies. Consider adding:
- Explanation of why cookies are preferred over localStorage for token storage
- CSRF protection recommendations when using cookies for authentication
- Token expiration and refresh token patterns
- Security implications of different cookie configurations
Here's a suggested expansion of the introduction:
## Handling Authentication with Cookies
-You can manage authentication tokens using cookies like this:
+Cookies are often preferred over localStorage for storing authentication tokens due to their enhanced security features and protection against XSS attacks. Here's how to implement secure cookie-based authentication:
+
+::warning
+When implementing authentication, consider these security best practices:
+- Use `httpOnly: true` to prevent XSS attacks from accessing the token
+- Implement CSRF protection for cookie-based authentication
+- Consider token expiration and refresh token patterns
+- Use secure configurations like `secure: true` in production
+::
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
## Handling Authentication with Cookies | |
You can manage authentication tokens using cookies like this: | |
## Handling Authentication with Cookies | |
Cookies are often preferred over localStorage for storing authentication tokens due to their enhanced security features and protection against XSS attacks. Here's how to implement secure cookie-based authentication: | |
::warning | |
When implementing authentication, consider these security best practices: | |
- Use `httpOnly: true` to prevent XSS attacks from accessing the token | |
- Implement CSRF protection for cookie-based authentication | |
- Consider token expiration and refresh token patterns | |
- Use secure configurations like `secure: true` in production | |
:: |
const accessToken = useCookie('accessToken', { | ||
sameSite: 'strict', | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strengthen cookie security configuration.
The cookie configuration is missing important security options that are crucial for storing authentication tokens.
const accessToken = useCookie('accessToken', {
sameSite: 'strict',
+ httpOnly: true, // Prevent XSS attacks from accessing the token
+ secure: process.env.NODE_ENV === 'production', // Require HTTPS in production
+ maxAge: 7200, // Token expiration in seconds
+ path: '/', // Cookie accessibility path
})
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
const accessToken = useCookie('accessToken', { | |
sameSite: 'strict', | |
}) | |
const accessToken = useCookie('accessToken', { | |
sameSite: 'strict', | |
httpOnly: true, // Prevent XSS attacks from accessing the token | |
secure: process.env.NODE_ENV === 'production', // Require HTTPS in production | |
maxAge: 7200, // Token expiration in seconds | |
path: '/', // Cookie accessibility path | |
}) |
🔗 Linked issue
I haven't found an issue for it, but this doc can be enhanced once #20652 is closed.
📚 Description
Adds an example to the Nuxt documentation demonstrating how to manage authentication tokens using the
useCookie
composable.By providing a concrete use case for handling accessToken with cookies, this helps developers better understand how to manage authentication tokens in their Nuxt apps through a plugin. The example includes cookie configuration, login, and logout functionality, making it easier for users to implement token-based authentication in their projects.
This addition aims to improve the documentation by offering practical guidance on a common use case.
Summary by CodeRabbit
useCookie
composable documentation to include a new section on handling authentication with cookies.