You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However UAA as backend server does not handle this encoding, see existing issue on cloudfoundry/uaa#778
I would like to have a direction for a fix, means, use non RFC complient encoding in go-uaa (uaa-cli) or fix UAA .
Problem now it, that uaa-cli (client) and uaa (server) are not working together if special characters in secret
e.g.
client_id: admin
client_secret: admin#secret
The text was updated successfully, but these errors were encountered:
go-uaa uses oauth2 from standard go and this encodes authorization header according to standard
RFC, see
https://github.com/golang/oauth2/blob/master/internal/token.go#L195
However UAA as backend server does not handle this encoding, see existing issue on
cloudfoundry/uaa#778
I would like to have a direction for a fix, means, use non RFC complient encoding in go-uaa (uaa-cli) or fix UAA .
Problem now it, that uaa-cli (client) and uaa (server) are not working together if special characters in secret
e.g.
client_id: admin
client_secret: admin#secret
The text was updated successfully, but these errors were encountered: