英文:
How the IdentityServer processes the token request?
问题
IdentityServer如何处理请求并生成令牌？
它只处理HTTP请求吗，还是在我们使用gRPC进行请求时会在内部进行转换？如果我们遵循gRPC而不是HTTP请求，会出现问题吗？
我对此还不太了解，正在努力更好地理解它。
英文:
How the IdentityServer processes the request and generates the token?
Does it process only if its http request or it converts it internally if we make request using gRPC? Will there be an issue if we follow the gRPC instead of the http requests?
I am new to this and trying to understand it better.
答案1
得分: 1
identityServer遵循OpenID-Connect/OAuth2标准，因此仅支持通过HTTPS的请求。 gRPC不适用于验证用户请求。
另外，除了gRPC Web之外，gRPC在浏览器中的支持并不是很好，gRPC更适用于机器之间的通信。
不过，一旦您收到了令牌，您可以在gRPC请求中包含访问令牌以访问其他服务。
英文:
identityServer follows the OpenID-Connect/OAuth2 standards, and because of that it only supports requests over HTTPS. gRPC is not suitable for authenticating user requests.
gRPC is also not really well supported in the browser (besides gRPC Web), gRPC is more for machine-to-machine communication.
However, once you have received your tokens, you can include the access token in gRPC requests to other services.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论