mockoidc

mockoidc copied to clipboard

How to add additional claims to the token?

3

Services often need to add their own claims to tokens to manage what users are allowed to do in a system. OIDC providers like Okta, Auth0, and others allow their...

BenjamenMeyer

- Create a custom user type in order to add new claims; it is in the test package space in order to be external to mimic how users would need...

BenjamenMeyer

Ignore ordering of openid token in scope parameter

1

Change the logic that checks for the "openid" token in the "scope" parameter value to ignore ordering. The Scopes section of the specification appears to only require that "openid" be...

jimrobinson

`client_secret` should be optional with authorization_code + PKCE flow

3

Since this flow is intended to be adopted by native and web apps, most of the services (such as auth0 for instance) allow to omit `client_secret`, as it's anyway insecure....

lanwen

Example Tests

1

It would be extremely helpful to have an example unit test and/or integration test to see how this all fits together.

BenjamenMeyer

jachym-tousek-keboola

I may be missing a section in the specification that discusses ordering dependencies, but my reading of https://openid.net/specs/openid-connect-basic-1_0.html#Scopes is that the order of the tokens in the "scope" parameter don't...

jimrobinson

Support sub in userinfo field

1

The Subject (sub) field is not returned on userinfo requests. According to https://connect2id.com/products/server/docs/api/userinfo#claims this is required. Added the Subject field and wired it like the other fields.

FerdinandvHagen

I encountered a data race when running parallelized tests with this library. The stack demonstrated a race between `NewSession()` performing a write operation on a map and `GetSessionByID()` performing a...

brad-defined

In using `mockoidc` with browser based testing scenarios for my web app, and I noticed that I don't have a lot of control/stability over how many times the OIDC IdP...

yorinasub17