Client Credentials - machine to machine #4763
Unanswered
vincentcordel
asked this question in
Help
Replies: 1 comment
-
Since, both are the web clients, is it really a machine-to-machine communication? Because, whatever token you store in the browser can be taken by a user and the same could be used to issue requests from another clients as-well. There are many similar discussion on the web related to this. For example: https://stackoverflow.com/questions/63180306/protect-a-public-api The TLDR is:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I use adonis as an API backend only.
I want to consume the api on multiple domains/subdomains using Vue (one app per domain)
Some routes should be public (unauthenticated user) and some private.
I'm a newbie so my excuses if it sounds obvious to you!
I can use access tokens guard to consume the API when a user is authenticated.
However I don't know how to consume the API for public routes (not logged in) while only restricting access to the API to the domains/subdomains.
I come from Laravel where I could use the passport package with client credentials grant tokens https://laravel.com/docs/11.x/passport#client-credentials-grant-tokens
But I don't know how to do it with Adonis (in addition to the access tokens guard).
Any help would be appreciated!
Thanks :)
Vincent
Beta Was this translation helpful? Give feedback.
All reactions