dotnet
Authorization header, OpenID Connect implicit flow authentication
Is it on your roadmap to support authorization headers, and possibly to support OpenID Connect standards based implicit flow authentication through a browser popup?
More explicit support for authorization is definitely being considered. You can set authorization headers now (see the set header command, and the -h|--header arguments of the get/post/etc commands), but we recognize that its a bit manual.
I can only speculate on the implicit flow, but my sense is that would be lower priority because of the focus on fast command line dev/test scripted scenarios. But we'll see what people ask for!
I do feel this would be quite a common use case, especially for bearer token. Not being able to do "set auth bearer
Although we can always do "set headers authorization bearer
I would like to set aside some time to talk with my buddy @cmatskas about some ideas here and if AAD team would be interested in this implementation.
Anything that can help with secure authentication via AAD. Adding @John Patrick Dandisonmailto:[email protected] as well
From: Brady Gaster [email protected] Sent: Monday, June 22, 2020 12:12 To: dotnet/HttpRepl Cc: Christos Matskas; Mention Subject: Re: [dotnet/HttpRepl] Authorization header, OpenID Connect implicit flow authentication (#156)
I would like to set aside some time to talk with my buddy @cmatskashttps://github.com/cmatskas about some ideas here and if AAD team would be interested in this implementation.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dotnet/HttpRepl/issues/156#issuecomment-647720429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA7PQHTU4NN2K5CNMICDBIDRX6UKDANCNFSM4IKR6K7Q.
