|
Hello, |
Replies: 4 comments 1 reply
|
Password grant type is not something you'd use for a backend integration. That's what you would use when you have an actual user trying to login with username and password. So you also wouldn't have that username and password as properties, but instead would have some kind of UI where the user would enter those. |
|
i assumed my one BE service 1 is a client for another BE service 2 (resource server on graphql-java-kickstart/graphql-spring-boot). Accordingly, service 1 keeps in itself username and password, and could receive token without UI. ok Another question. If I create a custom (my) WebClient , then your GraphQLWebClient will use my WebClient or yours WebClient created by this starter, |
|
You're first paragraph is correct, that is how it works. But that's the client credentials grant you're describing here. But instead of username and password it's using the client id and secret in a similar way. Make sure to read up on the various available grants and usages instead of asking that kind of details here. The https://auth0.com site has nice documentation about the various flows. Regarding your other question. As you can see in the autoconfiguration class it'll create a WebClient instance in case it's missing. So if you're already providing a WebClient bean, then it'll use that one. That's normal Spring Boot convention. See: . |
|
Thanks for your answers |
|
Sure thing. Can you ask it in the Discussions section next time? Issues are really for bugs, not general questions like this one. |
You're first paragraph is correct, that is how it works. But that's the client credentials grant you're describing here. But instead of username and password it's using the client id and secret in a similar way. Make sure to read up on the various available grants and usages instead of asking that kind of details here. The https://auth0.com site has nice documentation about the various flows.
Regarding your other question. As you can see in the autoconfiguration class it'll create a WebClient instance in case it's missing. So if you're already providing a WebClient bean, then it'll use that one. That's normal Spring Boot convention. See:
graphql-spring-webclient/graphql-webclient-sprin…