encoding issue #24
encoding issue #24
Conversation
|
Hey strehle! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/159169771 The labels on this github issue will be updated when the story is started. |
* with new behaviour the client authentication is not set to header but to http body * no Authorization * check body for client_id and client_secret
|
Hello @strehle, we have begun working with the Go CLI and plan to accept your PR. We've created a story to represent the change: https://www.pivotaltracker.com/story/show/166970393 |
|
Hello @strehle - providing update. We have begun looking into the proposed change via the story mentioned above (#166970393). We intend to correct the issue, but are considering alternative implementation approaches as we review the CLI, but also underlying UAA implications. |
|
Hello @dbeneke sure you can do it in like you want and if you fix UAA , great. The authorization via Header is in UAA not Oauth2 compliant but if uaa-cli uses the body to provide client id/credentials there is no issue with uaa, therefore this way. |
|
Client secret encoding has now been fixed in UAA and the CLI |
#23