Giter Club home page Giter Club logo

Comments (4)

geromegrignon avatar geromegrignon commented on July 18, 2024

Hi @Niyaco,

I can reproduce it.
I'm starting local tests right now to identify the bug.

from realworld.

geromegrignon avatar geromegrignon commented on July 18, 2024

I'm quite busy right now handling it but based on my first tests, it's due to using the username from the token on backend side to find the user to be updated.

It happens by firstly updating the username.
On consequential tries, you still have the same token with the old username.
The API consumes it to find the user to be updated, but there is nothing to be found.

from realworld.

rahulthedevil avatar rahulthedevil commented on July 18, 2024

I'm quite busy right now handling it but based on my first tests, it's due to using the username from the token on backend side to find the user to be updated.

It happens by firstly updating the username. On consequential tries, you still have the same token with the old username. The API consumes it to find the user to be updated, but there is nothing to be found.

Then why not use something that does not change to generate the token? Maybe user id? If it seems that it may cause security issue, then why not create one unique id for each user only to use it for access token and it will never change and eliminate all data from token which can be changed by user

from realworld.

geromegrignon avatar geromegrignon commented on July 18, 2024

I'm quite busy right now handling it but based on my first tests, it's due to using the username from the token on backend side to find the user to be updated.
It happens by firstly updating the username. On consequential tries, you still have the same token with the old username. The API consumes it to find the user to be updated, but there is nothing to be found.

Then why not use something that does not change to generate the token? Maybe user id? If it seems that it may cause security issue, then why not create one unique id for each user only to use it for access token and it will never change and eliminate all data from token which can be changed by user

Yes exactly, that's what I have in mind (there is already a unique id for each user, but not exposed to the API currently).

from realworld.

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.