-
Notifications
You must be signed in to change notification settings - Fork 495
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
Switching from builtinuser table to authenticatedusertable for certain pages #1450
Comments
I think this is all set for 2 and 3. 1 is a bit messy, so I suggest deferring display of account info for none built in (since they also cannot edit) to 4.0.x. |
Passing to QA to confirm 2 & 3. Please send back to me after that so I can decide what to do with 1. thanks! @kcondon |
OK, 2,3 look good both with builtin and shib user. Passing back to Liz as requested. |
We will the text from the Account Information edit dropdown appear in this tab instead of there. |
@mheppler Currently when a user logs in via Shibb and goes to their account page, they see this: When they click on the Account Info dropdown, they see this: We need to move the text from that dropdown (so only API Token is left) and have it displayed in the Account Information tab. However, that texts doesn't make sense so it should say: "You are logged in through your institution so Dataverse is not able to display your account information. If you need to update any of this information, please contact your institution." |
Added back user.toEditDetail message to bundle, and revised it to the suggested, updated text. Moved it from Account Information dropdown to the Account Information tab on the Account page. |
This is what was decided for 4.0, rather than remove the tab (hence @equigley adding her comments). One quick note: it's not that we can't display your account info (because we will in a future version, or at least the parts we get from shib, etc), so I think that line is a little misleading. Can we remove it? So: "You are logged in through your institution. If you need to update any of this information, please contact your institution." |
Updated logged in Shibboleth info from #1450
OK, message is there. @eaquigley wording is not exactly as you specified but seems close enough. Closing. |
Currently the builtinuser table is being used to populate information on:
however, since we have moved some components of the builtinuser table to the authenticateduser table, we need to change it so these pages are calling from the authenticateduser table.
The text was updated successfully, but these errors were encountered: