[bug] Authentication from ELK web client #439

New Issue

Open

opened 2023-01-19 09:34:45 +00:00 by edimitchel · 2 comments

edimitchel commented

2023-01-19 09:34:45 +00:00

Your setup

OTP

Extra details

No response

Version

No response

PostgreSQL version

No response

What were you trying to do?

Hi,

As you probably see, a new web client is born which proposes good UI/UX: elk.

I'm trying to connect my account hosted on fr.disroot.org (which is powered by Akkoma).

On login, I'm redirected to https://elk.zone/api/fe.disroot.org/oauth?origin=https://elk.zone

{
	"url": "/api/fe.disroot.org/oauth?origin=https://elk.zone",
	"statusCode": 422,
	"statusMessage": "Missing authentication code.",
	"message": "Missing authentication code.",
	"stack":""
}

I'm posting this issue here because I didn't encountering this issue on another Mastodon instance.

Thank you for the effort!

What did you expect to happen?

What actually happened?

No response

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details _No response_ ### Version _No response_ ### PostgreSQL version _No response_ ### What were you trying to do? Hi, As you probably see, a new web client is born which proposes good UI/UX: [elk](https://elk.zone). I'm trying to connect my account hosted on fr.disroot.org (which is powered by Akkoma). On login, I'm redirected to https://elk.zone/api/fe.disroot.org/oauth?origin=https://elk.zone ```json { "url": "/api/fe.disroot.org/oauth?origin=https://elk.zone", "statusCode": 422, "statusMessage": "Missing authentication code.", "message": "Missing authentication code.", "stack":"" } ``` I'm posting this issue here because I didn't encountering this issue on another Mastodon instance. Thank you for the effort! ### What did you expect to happen? Login without issue as it works fine with another mastodon instance ### What actually happened? _No response_ ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

edimitchel added the

bug

label 2023-01-19 09:34:45 +00:00

floatingghost commented

2023-03-08 17:45:31 +00:00

Owner

using current elk, i was able to authenticate against 3.6.0 without issue - can you check this again?

snott commented

2023-09-08 21:58:00 +00:00

I got this same result, however I have Authorised Fetch enabled so assume it is because of that?
I may try local Elk install (haven't looked at this yet) and see i that works as a proper local FE.

I got this same result, however I have Authorised Fetch enabled so assume it is because of that? I may try local Elk install (haven't looked at this yet) and see i that works as a proper local FE.

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#439

No description provided.