Releases: cloudfoundry/cf-uaac
4.3.0
Bumping dependencies
Authors: @bruce-ricard and @ccjaimes
Contributors
Assets 2
4.2.0 Release
Bug Fix
UAAC now encodes client credentials correctly.
This version of the CLI is required for UAA versions 74.0.0 onward in order to handle secrets containing special characters.
Available on Rubygems.org
Known Issue
For UAA server versions 74.0.0 onward, if UAA server's bosh property uaa.authentication.enable_uri_encoding_compatibility_mode is set to true, UAA server will only URI-decode basic auth credentials when the X-CF-ENCODED-CREDENTIALS header is set to true.
And since UAAC 4.2.0 always encodes client credentials when sending requests to UAA server, and since UAAC 4.2.0 does not have the option to add X-CF-ENCODED-CREDENTIALS header, commands such as uaac token client get might not work when uaa.authentication.enable_uri_encoding_compatibility_mode is set to true; particularly, if the client secret passed to UAAC includes special characters, the server would not decode the secret correctly.
4.1.0 Release
4.0.0 Release
- Fixed bug where origin of group members were being incorrectly assigned based on the origin of the user, causing group memberships to be lost on external user login.
- Removed the functionality for group reader and group writer which have been deprecated.
3.13.1 Release
Bug fix for adding users to groups that contain other groups as members.
3.13.0 Release
Bump cf-uaa-lib to 3.10.0 to fix the issue with loading the OS trust store
3.12.0 Release
uaac user add does not prompt for password if an origin is specified.
3.11.0 Release
Adds --origin parameter to user operations, for specifying commands against specific IDPs.
3.10.0 Release Notes
This release fixes a problem where the uaac context was incorrectly showing a cached refresh token during client credentials grant type.
3.9.0 Release
https://www.pivotaltracker.com/story/show/141609057
Changed the /check_token invocation to use HTTP POST with a method.