Admins wants to see usernames in the table of users

[jedelbo]

I use Realm Studio 0.0.1-alpha.8 and ROS 2.0.0-alpha.35.

When I browse the users, I am presented with long numbers in stead of names.

[cmelchior]

I just ran into this. This is highly annoying when debugging.

I guess it is difficult to choose what to show here if people are using custom auth, but the username from the Password/Username provider would be much more useful.

Perhaps add a selector to choose what is shown under ID?

[bigfish24]

Yeah and we should store the username as metadata. I can update ROS to do this. In addition, we could just have logic to show usernames when the user has one vs the userId.

[cmelchior]

Having an Accounts section on the right side in the panel would probably also be useful. Similar to `metadata

[bigfish24]

@kraenhansen how do you plan to make this work?

[kraenhansen]

@bigfish24 I am thinking about showing a comma separated list of the users accounts[].providerIds (most users would have only one) instead of the ROS user ID ... in the table cell.

And then on the user sidebar, these providerIds will be shown in the title (instead of the ROS id), but as a badge that the user can hover to see which provider the id relates to.
And then demote the ROS user ID to something secondary, smaller text underneath the list of account id badges.

Something like this:

[bigfish24]

Yeah this seems reasonable, but I would include the ProviderId and UserId in the table so it can be searched on.

ProviderId(s)	UserId	Role	# Realms
af@realm.io	235072360327603285732	Administrator	2

Note to add the searching on ProviderId because realm-js doesn't support subquery you will need to search on Account then use backlinks to retrieve the list of User objects that match. This could make it hard to combine searching on UserId and ProviderId thoughts?

[kraenhansen]

I think its a good idea to show both ids in the table. But since it's a table of users, wouldn't ID be better than UserId? The User-prefix feels redundant to me.

[bigfish24]

@kraenhansen I think if you have both we should always use the terminology used elsewhere. When using custom auth you need to know the difference (though I guess we could argue for different naming everywhere). Currently, the userId is the stable ID used by ROS to identify a user, whereas the providerId is the external ID used to identify the ROS user. By default these are different in our implementations of auth providers, but you are free to actually have them the same with custom auth, assuming you can guarantee that the custom auth or providerId is unique and stable. We can't guarantee that with username/password since a username does not meet the requirements for a userId.

[kraenhansen]

Ahh okay - I see. The User class indeed has a column named userId, then it makes sense to give it that name in the table too.
I would argue that the name in the class could just be id, but that will be for another issue :)