uaa list-clients: json: cannot unmarshal string into Go struct field Client.resource_ids of type []string about uaa-cli HOT 4 OPEN

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

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

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

from uaa-cli.

• According to UAA API specs, GET /oauth/clients/{client_id} should return resource_ids attribute as an Array.
• Actual UAA implementations return resource_ids either as an array of strings or as a simple string.

Example of querying UAA v4.19.2:

$ uaa curl /oauth/clients|jq '.resources[]|select(.resource_ids|type == "string")'
{
  "scope": [
    "cloud_controller.admin",
    "cloud_controller.read",
    "cloud_controller.write",
    "openid",
    "zones.*.*",
    "zones.*.*.*",
    "zones.read",
    "zones.write",
    "scim.read"
  ],
  "client_id": "identity",
  "resource_ids": "none",
  "authorized_grant_types": [
    "authorization_code",
    "client_credentials",
    "refresh_token"
  ],
  "redirect_uri": [
    "REDACTED",
    "REDACTED*"
  ],
  "autoapprove": true,
  "authorities": [
    "zones.read",
    "zones.write",
    "scim.zones",
    "uaa.resource",
    "uaa.admin",
    "cloud_controller.admin"
  ],
  "lastModified": 1551175600000
}

So, even with uaa-cli is API compliant, it is not compatible with the actual UAA servers.

from uaa-cli.

Just to follow up

$ uaa version
0.10.0 8626b94

OM/PAS = 2.8.5

Problem persists.

from uaa-cli.

Hello. The /oauth/clients api does have some quirks and I agree that this cli should handle those.

We don't have plans to start work on this CLI again at the moment, but if we do this issue will be addressed then.

from uaa-cli.