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 login flow gets invoked. So I'm finding myself resorting to have mockoidc returning the same user. Ideally, I can use the default user, but since I am only integrating with one OIDC provider (Azure AD B2C), the expected ID Token claims format doesn't match.
To address these two issues, I've been simply packing the queue an arbitrary number of times with the same user, but it would be great if I can just override the default user that is returned.
This PR adds a SetDefaultUser function that does just that.
In using
mockoidcwith 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 login flow gets invoked. So I'm finding myself resorting to havemockoidcreturning the same user. Ideally, I can use the default user, but since I am only integrating with one OIDC provider (Azure AD B2C), the expected ID Token claims format doesn't match.To address these two issues, I've been simply packing the queue an arbitrary number of times with the same user, but it would be great if I can just override the default user that is returned.
This PR adds a
SetDefaultUserfunction that does just that.