-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth: OAuth 2.0 #1003
Comments
Really important feature <3 |
So far this is the only thing keeping me attached to Postman. Really keen to see this implemented. |
We would love to move to Bruno as well, but since we are requiring |
Dependend on what you need you might want to check this as a workaround for e.g. the Client Credentials flow. @Rens660 - I've got quite a similar one for Authorization Code. You'll need to do one manual step in the browser, but atleast it returns e.g. the corresponding link as part of an error message. Would you be interested in that? |
Hi @tsteckenborn, |
I will be building OAuth 2.0 functionality in this upcoming live coding stream with Hussain on Dec 16th |
Take a look if that helps to ease the usage |
Pretty much the only thing tying me to insomnia. We use the implicit flow on our end. |
Can't wait for this! |
FYI: Implicit flow is deprecated, should not be used any more (replaced by Authorization code + PKCE) |
Thanks for the heads up, though I don't see Authorization code + PKCE supported here yet either. I'll have to check to see if we have migration plans from Implicit flow. |
Is there any progress on the OAuth2 support? |
@helloanoop can you give any news on your progress or estimation when you continue on OAuth 2 support? The past weeks were very quiet around OAuth 2 😢 |
Thanks for your patience. I was a bit tied up in working on the lang improvements that will be needed to unblock some other features in the pipeline. Given the immense pain point and upvotes on this feature, I will spend some time on this week on this ticket and will share some updates towards the end of this week. |
Hej @helloanoop :) Some weeks passed by and i guess the implementation could be more complicated then expected. Have you gained more insights on how you can proceed? |
Hey @fuxx Appreciate your patience. A big blocker was the Bru Lang design which I wanted to complete. This was very important to ensure that we have a way forward to introduce more features in the future and seamlessly allow folks to migrate to the new format (expected to be available by end of Feb) Now there are two things in my pipeline
I am not touching any other feature (except critical bugs) unless above 2 are launched. |
Any news about OAuth 2.0 support? |
…s, authorization code, client credentials
…ble by scripts The new variable 'credentials' is now available in 'req' object. It is added automatically during request preparation if oauth2 method is used and is value is either evaluated or retrieved from collection oauth2 cache. usebruno#1003
…Token action The actual the authorization request is part of request preparation usebruno#1003
…e - sort tokens first. Blur unfocused tokens for privacy. usebruno#1999 usebruno#1003
…word credentials grant types -- missing client id & secret for password grant type (usebruno#2051) * fix(usebruno#1003): content type for client_credentials & password grant types * feature(usebruno#1003): added client is & secret for password credentials grant type
…from preferences when accessing Auth and Token URLs (usebruno#2071) usebruno#1684 usebruno#1003
…aracter from the response body (#2346) * fix(#1003): content type for client_credentials & password grant types * feature(#1003): added client is & secret for password credentials grant type * fix: filter out non-printable control character and ZWNBSP character * fix: filter out non-printable control character and ZWNBSP character
…t parse logic (#2351) * fix(#1003): content type for client_credentials & password grant types * feature(#1003): added client is & secret for password credentials grant type * fix: filter out non-printable control character and ZWNBSP character * fix: filter out non-printable control character and ZWNBSP character * remove ZWNBSP character from response body --------- Co-authored-by: Anoop M D <anoop.md1421@gmail.com>
@helloanoop would it be possible for the Oauth2 implementation in Bruno to send extra headers/body request parameters. For example: we use Auth0 and we require a "organisation" request parameter to be send to the Oauth2 authentication endpoint. Currently, there is no functionality to send anything extra with the request. |
Is there any update on this topic, can´t wait to see OAuth 2 auth flow without scripting in Bruno 🙂 |
…from preferences when accessing Auth and Token URLs (usebruno#2071) usebruno#1684 usebruno#1003
…aracter from the response body (usebruno#2346) * fix(usebruno#1003): content type for client_credentials & password grant types * feature(usebruno#1003): added client is & secret for password credentials grant type * fix: filter out non-printable control character and ZWNBSP character * fix: filter out non-printable control character and ZWNBSP character
…t parse logic (usebruno#2351) * fix(usebruno#1003): content type for client_credentials & password grant types * feature(usebruno#1003): added client is & secret for password credentials grant type * fix: filter out non-printable control character and ZWNBSP character * fix: filter out non-printable control character and ZWNBSP character * remove ZWNBSP character from response body --------- Co-authored-by: Anoop M D <anoop.md1421@gmail.com>
Bruno is great! And I'd also love to see the OAuth2 auth flow (grant type client credentials) completed, so I fully recommend it everywhere I can :-) |
Parent Issue: #119
Support OAuth 2.0
The text was updated successfully, but these errors were encountered: