Skip to content
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

Client resource_ids should always be an array #1287

Closed
sneal opened this issue May 12, 2020 · 2 comments
Closed

Client resource_ids should always be an array #1287

sneal opened this issue May 12, 2020 · 2 comments
Labels
accepted Accepted the issue

Comments

@sneal
Copy link

sneal commented May 12, 2020

What version of UAA are you running?

74.5.5

How are you deploying the UAA?

I am deploying the UAA as part of a Tanzu Application Service.

What did you do?

Executing uaa get-client identity against a Tanzu Application Service installation, cloudfoundry/uaa-cli#63

What did you expect to see? What goal are you trying to achieve with the UAA?

I would expect the UAA server to honor the data contract and always return an array for client resource_ids.

What did you see instead?

Resulted in json: cannot unmarshal string into Go struct field Client.resource_ids of type []string. It seems the builtin identity client returns a single string for the client's resource_ids instead of an array.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/172783660

The labels on this github issue will be updated when the story is started.

@shamus
Copy link
Contributor

shamus commented May 21, 2020

Hi there. While I agree that the uaa cli should be able to handle the responses coming from the UAA API.

Closing this issue in favor of cloudfoundry/uaa-cli#63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Accepted the issue
Projects
None yet
Development

No branches or pull requests

3 participants