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
A user attempted to access their "Your Uploaded Data" through the link https://portal.edirepository.org/nis/userBrowseServlet , which requires a "vetted" login session. In this case, however, the user signed on with an Orcid, which provides only an "authenticated" session. The user is repeatedly sent back to the login page without any indication that the type of login being used is not sufficiently privileged to access the "Your Uploaded Data" web page.
It's been a while since I logged in at EDI and I've since moved to a new computer. Somewhere along the line, I've lost my login info. I can log on via my orcid account, but then when I try to go to my uploaded datasets, it bumps me back to login and wants username and password, both of which I've lost track of.
The "Your Uploaded Data" (and likely the "Your Data Cart") web page(s) should notify users that only a "vetted" login session (one with an LDAP account) is required.
The text was updated successfully, but these errors were encountered:
servilla
changed the title
UX: Attempting to access "My Uploaded Data" with an OAuth sign-on results in a login loop
UX: Attempting to access "Your Uploaded Data" with an OAuth sign-on results in a login loop
Dec 6, 2024
A user attempted to access their "Your Uploaded Data" through the link
https://portal.edirepository.org/nis/userBrowseServlet
, which requires a "vetted" login session. In this case, however, the user signed on with an Orcid, which provides only an "authenticated" session. The user is repeatedly sent back to the login page without any indication that the type of login being used is not sufficiently privileged to access the "Your Uploaded Data" web page.The "Your Uploaded Data" (and likely the "Your Data Cart") web page(s) should notify users that only a "vetted" login session (one with an LDAP account) is required.
The text was updated successfully, but these errors were encountered: