[16:56:06] TypeError: request.charCodeAt is not a function
at Function.Module.resolveLookupPaths (internal/modules/cjs/loader.js:408:15) at Function.Module.resolveFilename (internal/modules/cjs/loader.js:574:20)
at Nuxt.resolveModule (F:\Javaspace\general\general-card-www\node[email protected]@nuxt-edge\dist\nuxt.js:2178:35) at Nuxt.resolveAlias (F:\Javaspace\general\general-card-www\node[email protected]@nuxt-edge\dist\nuxt.js:2193:29)
at Array.map (<anonymous>)
at Builder.watchFiles (F:\Javaspace\general\general-card-www\node[email protected]@nuxt-edge\dist\nuxt.js:3878:37) at Builder.webpackDev (F:\Javaspace\general\general-card-www\node[email protected]@nuxt-edge\dist\nuxt.js:3829:10)
at Promise (F:\Javaspace\general\general-card-www\[email protected]@nuxt-edge\dist\nuxt.js:3755:23)

Hi, Guy

I'm using Oauth2 Facebook login by setting response_type code to the server for making authentication. I'm using Laravel Socialite with JWT-Auth to generate a token. Then the user has been authenticated the server will generate the token with response type JSON. I'm want to know how to pass the token to front-end Vue.js app.

nuxt-config.js (Auth Module)
auth: { strategies: { facebook: { client_id: process.env.FACEBOOK_CLIENT_ID, userinfo_endpoint: 'https://graph.facebook.com/v2.12/me?fields=about,name,picture{url},email,birthday', scope: ['public_profile', 'email', 'user_birthday'], redirect_uri: `${process.env.APP_URL}/oauth/facebook/callback`, response_type: 'code' } } }

After authenticate from server

Thanks in advance for any help that you are able to provide.

What problem does this feature solve?

Instead of making a separate call to an API endpoint for user data, it would be nice to be able to simply access the username that already exists inside the encoded JWT data object.

A simple function like the following (that takes advantage of jwtDecode) would suffice:

function getPayload(token) {
    var payload = null;

    try {
      payload = token ? jwtDecode(token) : null;
    } catch (_) {}

    return payload;
  }

This will provide the JWT's data object, like:

{ 
   username: "JohnDoe",
   scope: "user"
}

What does the proposed changes look like?

Offer a method to access the JWT payload directly

What problem does this feature solve?

When a token is added manually Axios doesn't attach the token. As for my auth flow it is required.

What does the proposed changes look like?

When setting a token manually using $auth.setToken calling this.$auth.ctx.app.$axios.setHeader(this.options.tokenName, token) this would solves the manual login problem.

Hello there, and thank you for your work on this project.
I am trying to authenticate against Keycloak, and have until now been using the closed branch https://github.com/nuxt-community/auth-module/pull/190

If I have understood things correctly, the PR was declined because the module is going to be refactored so that providers(like keycloak) are not part of the module, but instead imported as their own modules.

I have two questions:
1: What's the current status of the refactoring, and Keycloak? What do you recommend me doing going forwards?

2: @robsontenorio 's branch had some issues where the user was not logged in after redirect, but the cookies was set, so a refresh would log in the user. Also, logout did not work at all, do you(@robsontenorio) have any any tips or ideas about this? :)

Hope you can help, I really appreciate your work!

Hi! I’m working on a trusted app and I’d like to implement in-app authentication using Oauth2’s Resource Owner Password Grant, but I cannot for the life of me figure out how to with the Nuxtjs Auth module.

Is it even possible? And if so, can someone point me in the right direction? The docs aren’t very helpful.

Thank you!

I have a backend server (in Symfony) which also has oauth server. I can login with curl:

$ curl -X POST -d "client_id=...&client_secret=...&grant_type=password&username=...&password=..." example.com/oauth/v2/token
{"access_token":"...",expires_in":3600,"token_type":"Bearer","scope":null,"refresh_token":"..."}

Then I just need to add access_token from the response to every API call.

How can I use that login with auth-module?

I'm hosting my Nuxt PWA app on S3, but can't log in with laravel.passport because once I receive the code the module attempts to POST to _auth/oauth/laravel.passport/authorize, but S3 can't support POST requests and there is no directory like _auth in the dist after running nuxt build. How can I use laravel.passport on a client-side PWA hosted on S3?

I see that the laravel.passport provider calls addAuthorize which in turn deletes the client_secret, so its not visible in the dist code. How can I delete the client_secret when using a custom scheme?

I'm able to log in without a problem using a custom strategy, but upon refresh I'm logged out again. This happens only on the live/dist version of the pwa after running npm run generate. Looking at the storage, it seems that the cookies are still set upon refresh but overwritten after the app loads.

When running in Dev, upon refresh the user is still logged in, as expected.

How do I keep the user logged in after refresh?

My source code

What problem does this feature solve?

Currently the suggested way to bind your own error hooks is by defining a custom plugin:

// plugins/auth.js
export default function({ $auth }) {
  $auth.onError((error, name, endpoint) => {
    console.error(name, error)
  })
}

And then extending the auth config like so:

{
  modules: {
    '@nuxtjs/auth'
  },
  auth: {
     plugins: [ '~/plugins/auth.js' ]
  }
}

But, the problem is that when some error happens during $auth.init().
In this case _errorListeners is not yet populated, so there's no way to intercept this error.

In my case this is token expiration error from one of the oauth providers.

How about providing any mechanism to handle errors during init()?

Hi,

We're using the auth module and we have been very satisfied so far… The issue now is that I have 2 different strategies and each one has it's own admin area, with different layouts and etc.

Is there any way to redirect to login/logout/redirect-page depending on the strategy?

Also, when logged in with one strategy @ /admin-1 (for example) and accessing /admin-2 (for example) allows me to see the content of the protected area even though I logged in with a different strategy.

Any thoughts about it?

Version

v4.5.1

Reproduction link

https://jsfiddle.net/

Steps to reproduce

Hi, in our registration process I am logging the user after successful registration. And then navigation should go to the second step of registration. This is the code sample:

                  await this.$api.Auth.register(this.registration);

                  this.$auth.loginWith('local', {
                        data: {
                            login: this.registration.email,
                            password: this.registration.password
                        },

                        headers: {
                            version: '0.0.1',
                            build: '0.1',
                            'client-type': 'WEB'
                        }
                    })
                        .then(async () => {
                            console.log('Inside login then block');
                            await this.$api.Auth.updateDevice(this.$store.state.device_details);
                            this.$router.push('/registration/2')
                        });

But after successful login something freezes the window. I can not even close the tab. Rest of the system works fine. But that particular tab is frozen. I can not figure out what is causing this issue. Is this something with my code or some internals of auth module that I am missing out?

What is expected ?

Flow should continue

What is actually happening?

screen frezzes.

hello, i have 3 subdomain with nuxt.js (1 nuxt SPA mode for 3 module apps - auth, admin, member) and 1 subdomain as api with lumen (laravel-microframework)..

auth.domain.com -> as single sign-on gateway (redirect to {member/admin}.domain.com if logged in / guest)
admin.domain.com -> as admin page (redirect to auth.domain.com if not logged in)
member.domain.com -> as member page (redirect to auth.domain.com if not logged in)

api.domain.com -> as a backend (PHP v7.0 using lumen - laravel microframework - without session)

i have a 2 question:

1. what should i do to integrate this with @nuxtjs/auth-module?
2. how to upload into shared hosting?

Sorry if it is irrelevant .
I checked on docs there is no info about calling custom function for login and user setting . As you can check into nuxt.config.js file

strategies: {
      local: {
        endpoints: {
          login: {url: '/WsUsers/login', method: 'post', propertyName: 'token.id', tokenName: 'authorization' },
          logout: false,
          user: {url: '/Workshops', method: 'get', propertyName: 'data'},
        },
        tokenRequired: true,
        tokenType: ''
      },
    },

here i want to call custom function which gets detail form server which i want an set it into auth.
Kinldy help.

Firstly, great job on the module and with the framework. Is it possible to return and store id_token from Auth0 as part of the integration? I need this to access and API endpoint from my app.

API

/api/auth/

{
"token": "uniq token",
"username": "name",
"email": "email"
}

nuxt

nuxt.config.js

strategies: {
local: {
  endpoints: {
          login: { url: 'approval/auth', method: 'post'},
          logout: false,
          user: false,
        },

login.vue

await this.$auth.loginWith('local', { data: this.form })
      .then(response => {
        this.$nuxt.$router.push('/')
        this.$axios.setToken(this.$auth.getToken(this.$auth.strategy.name))
        this.$auth.fetchUser();
        console.log(this.$auth.strategy)

i Viewed.
https://github.com/nuxt-community/auth-module/issues/144#issuecomment-390166011

Wondering if anyone managed to successfully implement auth-module in create-nuxt-app and having Express as the server-side framework. Stuck at implementing the local scheme since you have Express in server/server.js and if you implement the code in middleware/auth.js, you'll get:

WARNING  Compiled with 1 warnings
warning  in ./node_modules/express/lib/view.js

81:13-25 Critical dependency: the request of a dependency is an expression