We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
const $auth = useAuth() onBeforeMount(()=>{ userLogin() }) async function userLogin() { try { const response = await $auth.loginWith('discord') console.log(response) } catch (err) { console.log(err) } } </script>
// https://nuxt.com/docs/api/configuration/nuxt-config export default defineNuxtConfig({ devtools: { enabled: true }, modules: [ '@nuxt-alt/auth',"@pinia/nuxt" ], auth: { globalMiddleware: true, redirect: { login: "/", home: "/", callback: "/" }, strategies: { discord: { clientId: 'XXXXXXXXXXXXXXXXXXXXXX', clientSecret: 'XXXXXXXXXXXXXXXXXXXXXX' }, } } })
https://github.com/CowCatDE/nuxt-alt-auth-error
When the user authorizes himself via discord he gets a 400 Bad Request error.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
const $auth = useAuth()
onBeforeMount(()=>{
userLogin()
})
async function userLogin() {
try {
const response = await $auth.loginWith('discord')
console.log(response)
} catch (err) {
console.log(err)
}
}
</script>
Nuxt Config
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
devtools: { enabled: true },
modules: [
'@nuxt-alt/auth',"@pinia/nuxt"
],
auth: {
globalMiddleware: true,
redirect: {
login: "/",
home: "/",
callback: "/"
},
strategies: {
discord: {
clientId: 'XXXXXXXXXXXXXXXXXXXXXX',
clientSecret: 'XXXXXXXXXXXXXXXXXXXXXX'
},
}
}
})
Reproduction
https://github.com/CowCatDE/nuxt-alt-auth-error
Describe the bug
When the user authorizes himself via discord he gets a 400 Bad Request error.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: