-
Notifications
You must be signed in to change notification settings - Fork 492
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
Opening account settings gives server error for newly created account via remote (federated/institutional/Shibboleth or OAuth or OIDC) login #9029
Comments
Hello, we're having the same problem for accounts created via ORCiD. When clicking on the notification link, the user gets an "Internal Server Error". The error disappears when the user confirms her email. In our case, we didn't touch the option :ShowMuteOptions Our Dataverse installation is 5.11.1 Here's the error log:
|
@claudiodsf thanks for reporting this. The scenario you describe fits with what we're seeing. We're discussing a couple potential fixes, both contributed by the community: |
I just did a little testing with Shib and OAuth accounts. The bug is slightly different, which surprises me. tl;dr - With Shib you see the error immediately after clicking "Create Account" but with OAuth you have to click "Notifications". ShibOn https://demo.dataverse.org I had a colleague down the hall log in with his HarvardKey (Shibboleth) account. After checking the box to accept terms and clicking "Create Account" he immediately saw an Internal Server Error. He didn't have to navigate anywhere, such as notifications. Obviously, this is a poor first impression to leave a new user with! He reloaded his browser and and error went away. No screenshots. Please use your imagination. 😄 OAuth (GitHub)Usually I use Shib to log into https://dataverse.harvard.edu but I just created a second account using GitHub (OAuth) to see if the bug is the same. Apparently it's slightly different. I didn't see an Internal Server Error after clicking "Create Account". When I clicked "Notifications" I saw Internal Server Error. (Still a terrible first impression.) I'll include some screenshots below. |
Hello, just to report that this issue (with shibboleth) happens regardless the value of ":ShowMuteOptions" in our case. The error appears at any of the pages: |
@sergejzr yes, unfortunately, I think you're right. @janvanmansum are you ok with me updating the title and description of this issue? As a heads up, even thought this bug has been around since 5.11, we're planning to put out a patch release (5.12.1) instead of waiting for a larger, minor release (5.13), partially in response to this bug. Here's where we'll work on release notes: |
What steps does it take to reproduce the issue?
When does this issue occur?
The setting(crossed out by @pdurbin per comment below):ShowMuteOptions
is set to trueWhich page(s) does it occurs on?
What happens?
The server log contains the following stacktrace:
To whom does it occur (all users, curators, superusers)?
What did you expect to happen?
Which version of Dataverse are you using?
Any related open or closed issues to this bug report?
#7492
Screenshots:
The text was updated successfully, but these errors were encountered: