Closed wknapik closed 2 years ago
With --auth-user-header=x-amzn-oidc-data
passed to the server and an ALB in front, getting
time="2022-08-30T14:23:16Z" level=debug msg="Unauthenticated request"
time="2022-08-30T14:23:16Z" level=debug msg="Auth required"
time="2022-08-30T14:23:16Z" level=debug msg=anonymous
after a successful SSO login. Same setup works with older wireguard-ui (e.g. 1.3.0).
When I log the actual error, I get illegal base64 data at input byte 450
and/or token contains an invalid number of segments
, but it appears to be a valid ES256 token. jwt decode
doesn't complain.
Downgrading github.com/fujiwara/go-amzn-oidc from v0.0.3 to v0.0.2 appears to resolve the issue. Opened https://github.com/fujiwara/go-amzn-oidc/issues/7 for this.
Opened https://github.com/EmbarkStudios/wg-ui/pull/169 to address this via downgrade. There may be a better fix in the future, but this would unblock anyone affected by the issue who doesn't want to maintain their own fork and/or push/pull their own docker images.
Also the last release is a year old, so a new one would be useful anyway.
@suom1 can you please trigger a new release? I'm mostly interested in a new docker image myself. Thanks!
EDIT: I see there's a fresh latest
image, which is great, I can just pin to a hash, but it would be even better to have a tagged image.
Changes between embarkstudios/wireguard-ui
and
appear to have broken OIDC auth.
When logging into the webui, the user is not recognized and displayed as "anonymous" (unable to see their configs).
At the moment I don't have more info. I just know the downgrade to the older version fixes the problem. I'll post here if/when I know more, but figured it would be good to let you know asap.