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
{{ message }}
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
The user entity exists and pagination sections are correct, however the user that IBM returns is missing the username property. This causes our filtering to chop it out, thus an empty list is shown whilst user counts are correct.
I did some digging using their flavour of the cli and, when making like for like requests, they return a user containing the correct username property. The big difference is even though the api endpoint is set to https://api.eu-gb.bluemix.net they actually hit https://mccp.eu-gb.bluemix.net. I used this alternative host in the console and the username is now returned and everything works.
We should probably get more info from IBM before continuing
Is there anything we can do against the standard api.<region>.bluemix.net endpoint to fetch a user that contains a username?
What the mccp.<region>.bluemix.net endpoint is for, is it stable + accessible such as we can guide users to it (who enter the normal api url when registering an endpoint?)
they could call mccp if they wanted to - I think the main reason for "disabling" them is not performance but the fact that everything related to users (and their association to orgs and spaces) in bluemix has a cross-region aspect and therefore we proxy these through mccp. Remember, you create one org and our UX replicates that from US-south to EU-DE etc. if the user wishes so. Therefore I'd recommend stratos to do the same (although I am not sure if we ever made mccp an "official" API, it de-facto is one)
Use IBM Cloud for testing - you will be an non-admin.
Users lists ant org and CF level are empty - they should not be - the users count is shown as 1, but nothing is shown in the lists.
The text was updated successfully, but these errors were encountered: