I also have a strapi cms and another graphql server, so… two backends.
I want to secure the back-ends with Auth0, and I need them to be identity-aware for authorization reasons. So I started by setting up the cms as a machine-to-machine application, and then created an API and added the cms application to it.
Can I ask you to raise it as a GitHub issue in the repo you mentioned so that the repo maintainers can guide you how to use the stack they maintain to achieve that? Make sure to share the link with us so we can ping them. Thank you!
I guess my problem is that I don’t know whether I understand auth0 right.
My goal is that the user logs in with the front-end once, through Auth0, and then is able to make authenticated requests to backend services, including the strapi cms. It’s fine if the app has to do some kind of token exchange in order to make authenticated requests to backend services, and fine if the user has to confirm some extra permissions dialogs once. The back-end services need to be able to get the user profile so they can be identity aware. It’s not okay if the user has to log in more than once.
If anyone can describe how they can achieve that from an Auth0 perspective, that would be wonderful!