auth/token POST request --Invalid credentials given--

[BenK93]

Hey there! First of all thanks a lot you have done wonderful job! 🙏🏽 I'm running to en issue when I try to login through http://127.0.0.1:8000/auth/token I use the exact username and password, client id and secret are copied from admin panel

For example http://127.0.0.1:8000/auth/convert-token works perfectly fine

[visued]

+1

[vshia]

I'm running into the same problem and was wondering if you were able to figure out a workaround (or patch)? Thanks

[wagnerdelima]

Hi @BenK93,

I am assuming the convert-token endpoint is not enough for your needs? Did you overcome this issue?

I am sorry for the delayed response. It's that I've been really busy and I haven't got much help with this repo, so I am all alone to maintain it.

[Jrad84]

I had this issue too and fixed it by changing my backend application Authorization Grant type to Resource owner password-based. When I used Authorization code it gave me the "invalid client" error response.

[wagnerdelima]

Hi @Jrad84

Thanks for your message and for your investigation! I will leave this issue open so I can investigate it later.

[vishalmehta672]

http://127.0.0.1:8000/auth/convert-token

Where we get token?

[wagnerdelima]

I suggest you read the README file. It contains information about the endpoint.

[vishalmehta672]

I am use the exact username and password, client id and secret are copied from admin panel. can please suggest where I am doing mistake.

[Shodiev-Shokhrukh]

+the same

[wagnerdelima]

Nowhere in the documentation it suggests the grant_type to be password. Try replacing it by covert_token, instead.