Applying example to remix authenticator strategy

[keul]

I'm trying to use the Remix example

The error I get is:

Error: Strategy oidc not found.

What I noticed is that example configuration is authenticator.use(strategy);, which is not also passing a name (as documented in remix-auth.

I tried adding a name But doing this changed nothing:

let strategy = new OIDCStrategy<User>(
    {
      …
      authorizationParams: {},
    },
    async ({ profile, tokens }) => {
      const { email, name, sub } = profile;
      // …
    }
  );
authenticator.use(strategy, "oidc");

Also note that I has to add authorizationParams to make TS happy.

[keul]

About the name: forget it, inspecting the code I found that name parameter is optional read from the strategy object.

My problem seems related to configuration of the Issuer then, I've a long list of errors like:

    {
      received: 'HS384',
      code: 'invalid_enum_value',
      options: [Array],
      path: [Array],
      message: "Invalid enum value. Expected 'RS256' | 'RS384' | 'PS256', received 'HS384'"
    },
    {
      received: 'ES512',
      code: 'invalid_enum_value',
      options: [Array],
      path: [Array],
      message: "Invalid enum value. Expected 'RS256' | 'RS384' | 'PS256', received 'ES512'"
    },
    {
      received: 'PS512',
      code: 'invalid_enum_value',
      options: [Array],
      path: [Array],
      message: "Invalid enum value. Expected 'RS256' | 'RS384' | 'PS256', received 'PS512'"
    },
    {
      received: 'RS512',
      code: 'invalid_enum_value',
      options: [Array],
      path: [Array],
      message: "Invalid enum value. Expected 'RS256' | 'RS384' | 'PS256', received 'RS512'"
    }

Probably this is a misconfiguration on my side? I'm trying to use an OIDC service served by Keycloak

[sergiodxa]

I think I will need to add more possible values to the id_token_signing_alg_values_supported or token_endpoint_auth_signing_alg_values_supported or relax the validation to any string 🤔

[keul]

@sergiodxa yes, my impression was that those interfaces are too strict on possible values, or at least the list of possible values seems not updated enough.

[nouhoum]

Hi, I have the same issue with Ory Hydra. Some values are not taken into account in the enums.

Here is the ZodError content:

[
  {
    "received": "client_credentials",
    "code": "invalid_enum_value",
    "options": [
      "authorization_code",
      "refresh_token",
      "urn:ietf:params:oauth:grant-type:device_code",
      "urn:ietf:params:oauth:grant-type:jwt-bearer",
      "implicit"
    ],
    "path": [
      "grant_types_supported",
      2
    ],
    "message": "Invalid enum value. Expected 'authorization_code' | 'refresh_token' | 'urn:ietf:params:oauth:grant-type:device_code' | 'urn:ietf:params:oauth:grant-type:jwt-bearer' | 'implicit', received 'client_credentials'"
  },
  {
    "received": "offline",
    "code": "invalid_enum_value",
    "options": [
      "openid",
      "profile",
      "offline_access",
      "name",
      "given_name",
      "family_name",
      "nickname",
      "email",
      "email_verified",
      "picture",
      "created_at",
      "identities",
      "phone",
      "address"
    ],
    "path": [
      "scopes_supported",
      1
    ],
    "message": "Invalid enum value. Expected 'openid' | 'profile' | 'offline_access' | 'name' | 'given_name' | 'family_name' | 'nickname' | 'email' | 'email_verified' | 'picture' | 'created_at' | 'identities' | 'phone' | 'address', received 'offline'"
  },
  {
    "received": "token id_token code",
    "code": "invalid_enum_value",
    "options": [
      "code",
      "token",
      "id_token",
      "code token",
      "code id_token",
      "token id_token",
      "code token id_token",
      "none"
    ],
    "path": [
      "response_types_supported",
      5
    ],
    "message": "Invalid enum value. Expected 'code' | 'token' | 'id_token' | 'code token' | 'code id_token' | 'token id_token' | 'code token id_token' | 'none', received 'token id_token code'"
  },
  {
    "received": "pairwise",
    "code": "invalid_enum_value",
    "options": [
      "public"
    ],
    "path": [
      "subject_types_supported",
      1
    ],
    "message": "Invalid enum value. Expected 'public', received 'pairwise'"
  }
]

[heivo]

I have a similar validation problem with Azure AAD. Are there any plans to make schema validation less strict? Attaching my configuration and the resulting errors.

schema_validation_errors.json
openid-configuration.json