-
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
Shibboleth: Cannot convert a builtin account to shib, does not accept password. #3119
Comments
@kcondon I just tried this on https://shibtest.dataverse.org running v. 4.3.1 build develop-7fe7040 (the latest code in "develop" as of this writing) and converting a builtin account worked fine. Here are some screenshots: Here's what it showed in server.log (I must have it cranked up to fine):
I'm heading out for the day, but I'm passing it back to you for consideration, @kcondon |
OK, thanks. We need to get this working on the test box before we can mark this as resolved. |
On dataverse-internal running v. 4.3.1 build 95-68c7239 (latest from 2469-widgets branch), I'm able to replicate the problem of not being prompted to convert my account from local to shib. My first guess is that the leading spaces persisted in the database for my email address (see #2945 and #3044) are the problem:
|
Sure enough, after I eliminated the leading whitespace from my @kcondon I'm going to pass this back to you for consideration. #2945 was already closed as a duplicate of #3044. Perhaps #3044 should be worked on before we release 4.4. |
Was no longer able to reproduce, closing. |
Logging in via Shib using either Harvard or testshib on internal I can log in if there is no preexisting local account with the same email address. If there is a preexisting email, I need to convert the account on log in and that is currently failing with a bad password message, though the password is correct.
@pdurbin
This functionality was working when tested on internal during the QA phase. However, some minor tweaks were made during UX phase and there were some resolved merge conflicts.
The text was updated successfully, but these errors were encountered: