Closed LucaCinquini closed 8 years ago
I tracked this down to the fact that when a remote user logs into this site using the IdP selector, the user attributes are NOT transmitted. If instead the user types in the full openid, the attributes are propagated correctly. ESGF is not likely to drop support for the IdP selector, so we need to adapt. I think that the "All Node Users" table should be modified to show the user home node, and at least in the case of remote users, their openid instead of their last/first name and email. We should discuss this.
@LucaCinquini
since we get these funky looking accounts when the CU node says...this openID is not federated and since that results in a home node of CU, I am not sure the home node column does a whole lot of good because the home node is listed as CU for these foreign openids.
What do you think?
@LucaCinquini here is what it currently looks like:
I would leave the column for now, and possibly take it away later. I personally like to know where these users have their home page. thanks, L
On Mar 3, 2016, at 2:58 PM, Sylvia Murphy notifications@github.com wrote:
@LucaCinquini
since we get these funky looking accounts when the CU node says...this openID is not federated and since that results in a home node of CU, I am not sure the home node column does a whole lot of good because the home node is listed as CU for these foreign openids.
What do you think?
— Reply to this email directly or view it on GitHub.
luca suggests moving username to first column and ordering on that vice last_name.
done. verified on cu dev
Who: Luca
Sylvia noticed that the "All Node Users" table now shows at the top a lot of users who have no first name, last name, or openid. Must investigate.