GithubHelp home page GithubHelp logo

Comments (5)

joselfonseca avatar joselfonseca commented on June 1, 2024 1

this should be fixed in https://github.com/joselfonseca/lighthouse-graphql-passport-auth/releases/tag/6.0.2

from lighthouse-graphql-passport-auth.

joselfonseca avatar joselfonseca commented on June 1, 2024

Thanks for the the issue @canatufkansu

This pops up a question i've had for a couple of months. Do we really need to return the user from the refresh token mutation? The only reason we are using that parse token method is to read the JWT and get the user ID to query it and return it in the refresh token response, however I have a feeling we could just get rid of it as it may not even be necessary.

In your use case, do you need to get the user from that mutation?

from lighthouse-graphql-passport-auth.

canatufkansu avatar canatufkansu commented on June 1, 2024

Hi,

My mutation is like the following, I don't want to return the user information from the query but still get the error. As you said I'm using this mutation just for refreshing the token.

mutation {
  refreshToken(input: { refresh_token: "def502007bd3fb4746869a9aaeb17e07c56ff1328130ea4997f81387919a548a2ca5b71ed69468710b641070d7190992f481ddf7384b11ede288831cad22c8c7455417ca8b641f6c4103347f816a4b976500343a15a238f086a4234a3f91900e9891ed791e54aa4ed380b3433434e239824bb78a070b9da54f57d0a01db20d4014e45afb0a241064181794350123eacb95b410db4a775cc620b7b9dc2d97fea92884aba1907345323b95635fbea4b54c924ce86b7f84d8196a91de6e550dcb76cf7d462ccdef09213be5c794457f9b76c21b141822326fa8e8d0328ffa9b9242d02a7dfcdc6e0527d49670ee79115565c37b3133e6d6f0e5400004f565ffb0ab29c2c2033e0b1c16622b2ba714e0d49f0b633a00816d88ceafce168d2ae4c491dcabdf377ae95a6a548f143aceecbd3d0fc0e5b4267ba9c07944f52fd47dc386041ab0ad368eff9b56912522c6d13495ecbba7dc206a64ff2b449860eb56017b2cb32a7ac001" }) {
    token_type
    access_token
    refresh_token
    expires_in
  }
}

from lighthouse-graphql-passport-auth.

joselfonseca avatar joselfonseca commented on June 1, 2024

Ok, I think it will be a good idea to remove that code so it won't fail and since we don't really need to get the user from this mutation it will also remove some other issues that can happen. Will work on that.

from lighthouse-graphql-passport-auth.

joselfonseca avatar joselfonseca commented on June 1, 2024

Actually, I don't have to do that, I found another way. Fix coming

from lighthouse-graphql-passport-auth.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.