[bug] OAuth consumer mode broken #646
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#646
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
Debian 10, Elixir 1.15.4
Version
stable (
ebfb617b26
)PostgreSQL version
13.11
What were you trying to do?
Set up Akkoma to authenticate users using Keycloak, as we have in the past using pleroma.
What did you expect to happen?
Users can log in using keycloak.
What actually happened?
When trying to log in, the user is redirected to keycloak, then back to the callback url (
/oauth/keycloak/callback
), which is a blank page with code 500.Logs
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
For whatever reason,
state
is expected to be a JSON blob. I can't find this decoding happening inueberauth-keycloak
oroauth2
, and I'm not sure why it would be.Also mentioned here, but not reported:
Picking this up again: Looks like pleroma is on version
~> 0.4.0
of ueberauth, while akkoma is on~>0.10.0
.Between these versions, CSRF attack protection was added, and presumably the OAuth consumer mode code hasn't been updated for this.
Have tested with a few other providers and all seem broken.
[bug] OAuth consumer mode broken when using Keycloakto [bug] OAuth consumer mode broken