-
Notifications
You must be signed in to change notification settings - Fork 1k
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
OIDC login broken "TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'" #18816
Comments
#18670 was merged into 24.1 (which it shouldn't have been). Try reverting that ? |
Outch I see. I could rule out that social-auth was updated. This looks like a very good candidate. I will patch it locally and report back. Thanks. |
Ouch indeed. I'm sorry to see that my pull-request has broken something. I checked on our Galaxy instance and can reproduce the same error when I omit the "<oidc_endpoint>" element in the oidc_backends_config.xml file when configuring a oidc login provider as described here:
The error occurs when clicking the sign-in button. @bgruening can you maybe share what your oidc_backends_config.xml looks like? |
Sure, this is my config, that worked until a few days ago.
|
Fixed in #18818 |
Sorry about this, should have got merged into dev in retrospect. |
For what it's worth, I did some digging to figure out what exactly went wrong here. The short version is, I learned that some backends, like elixir, have a hard-coded OIDC_ENDPOINT that got overwritten with a None value because of the way I coded #18670 As a side note, I also found it interesting how some backends seem to prevent this problem by overriding this inherited function. But luckily you guys have already fixed it in #18818 Anyhow, I'll promise to be more careful with my next pull-request! 😇 |
Thanks @Edmontosaurus for looking into it! |
I'm not sure this is a Galaxy problem yet, but I thought I put this out while we are debugging it. It broke in the last days which is suspicious. It seems to only effect the ELIXIR OIDC on EU.
The text was updated successfully, but these errors were encountered: