Sign In Failed: TimeoutError: Timeout awaiting 'request' for 2500ms

[SamuelBradley]

Getting error when attempting to login using an OIDC connection.
Sign In Failed: TimeoutError: Timeout awaiting 'request' for 2500ms

Happens consistently on the first login attempt and usually works on the second attempt, with an OIDC connection to AWS Cognito. Doing some searching around the internets It may be linked to a default value in an OIDC middleware library. (https://devforum.okta.com/t/timeouterror-timeout-awaiting-request-for-2500ms/9878/5) Is the only related post on this issue I could find.

I've tried setting the timeout value for this plugin, but the default value of 10000ms already far exceeds the value cause an error.

[SamuelBradley]

We are using version 1.1.0 of the plugin

- name: magda-auth-oidc
    version: 1.1.0
    repository: https://charts.magda.io
    tags:
      - all
      - magda-auth-oidc

[t83714]

AWS cognito is not a standard OIDC implementation --- its implementation seems have some bug with URL encoding and incorrectly generate "nonce" when federate Active Directory.
We internally have a customised version to accommodate those issues --- I might release it sometime in future after make it more generic (it won't be in short term)
For your error, I suspect it's a different issue.

Have you add the OIDC issuer in your Magda config? Could you please provide your config?

[SamuelBradley]

Thanks for the response this is our OIDC magda config

# Cognito OIDC config
# Note: `issuer` & `clientId` are supplied through the `magda-oidc-config` secret
magda-auth-oidc:
  authPluginConfig:
    name: "XT Users"
  issuerName: "xt-dev-cognito-oidc"
  scope: "openid email"
  timeout: 10000

[t83714]

I don't think you can supplied "issuer" via secret?
It's passing from config here:

magda-auth-oidc/deploy/magda-auth-oidc/templates/deployment.yaml

Line 54 in ae58b51

"--issuer", {{ .Values.issuer | required "`issuer` is required for `magda-auth-oidc` chart." | quote }}

[t83714]

@SamuelBradley
I think this PR: #3 might fix your timeout issue.
Could you please have a test to see if it solves your issue? Thanks!
You can use test release version 1.2.2-alpha.0 to test it.