Skip to content
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

catch builtinuser e-mail field mismatch when Shibboleth is enabled #3184

Closed
donsizemore opened this issue Jun 24, 2016 · 1 comment
Closed

Comments

@donsizemore
Copy link
Contributor

This is possibly a tack-on to #2937 or possibly a suggestion, or possibly just noise.

During installation I set the dataverseAdmin account to my university address, with the intention that it be temporary until I found out where our archivists wanted such messages to go. Once I enabled Shib, a local login to the dataverseAdmin account found my e-mail address and dutifully offered to convert dataverseAdmin to a Shib account. I updated the address in the authenticateduser table but missed it in the builtinuser table. Until I found the mismatch in the database, dataverseAdmin login attempts would echo address mismatch SEVEREs to server.log but only present the login screen back to the end user, as if no login had been attempted.

We might want to add a note about this to the Shib docs, or maybe catch that error to send it back to the end-user in the browser, or since this is ultimately a Layer 8 Problem, close this issue and pardon my noise.

In any case, I hope you all have a great weekend!

@pdurbin
Copy link
Member

pdurbin commented Jun 24, 2016

I updated the address in the authenticateduser table but missed it in the builtinuser table

Hmm. I hope most users don't hack on database tables directly. Much better would be to change an email address via the GUI. I guess an API endpoint could be added some day.

Anyway, @donsizemore I'm glad you were able to recover. It sounds like the errors in server.log were helpful as-is. Thanks for the feedback. It's not noise. 😄

This vaguely related to #2170 which @bsilverstein95 is starting to look at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants