Closed BenK93 closed 2 years ago
+1
I'm running into the same problem and was wondering if you were able to figure out a workaround (or patch)? Thanks
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.
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.
Hi @Jrad84
Thanks for your message and for your investigation! I will leave this issue open so I can investigate it later.
Where we get token?
I suggest you read the README file. It contains information about the endpoint.
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.
+the same
Nowhere in the documentation it suggests the grant_type to be password. Try replacing it by covert_token, instead.
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 panelFor example
http://127.0.0.1:8000/auth/convert-token
works perfectly fine