-
Notifications
You must be signed in to change notification settings - Fork 17
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
Ability to disable Duracloud pieces on a test/dev system / breaks when can't authenticate to duracloud #75
Comments
Just so I understand the issue correctly, the stacktrace above occurs at the moment you attempt to log in via Shibboleth while the DuraCloud credentials are invalid? |
Yes. It might not be duracloud credentials being invalid but it happened when the service wasn't able to login. |
OK, noted. I'll try to replicate it. It's curious to me that Shib authentication causes the problem to occur, but as you mentioned RTS connections to DuraCloud should fail gracefully and be logged. |
One more question, do you get the same stack trace if you attempt to log in via the usual username/password authentication? |
We don't have a local username/password authentication, so I did not
attempt that.
…On Fri, Sep 27, 2024 at 5:27 PM Nicholas Woodward ***@***.***> wrote:
One more question, do you get the same stack trace if you attempt to log
in via the usual username/password authentication?
—
Reply to this email directly, view it on GitHub
<#75 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALBHSACMTDW47YCWCE7MP3ZYXLWZAVCNFSM6AAAAABM7C2ZIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGIZTANRUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I think I have a solution that will catch the exception before it rises up the ladder. I can't reproduce the error using the regular username/password, and I don't have access to a test Shibboleth authentication. I've confirmed that the RTS with 6b652b4 still works with both METS and BagIt consumers. Is there any chance you could test that commit in your environment? |
From what I can tell is if RTS is enabled and unable to connect to duracloud it breaks authentication such as Shibboleth
Not sure if there is a way to gracefully fail instead of throwing exceptions when duracloud isn't available.
This is at least on DSpace 7.6.2
The text was updated successfully, but these errors were encountered: