Closed ryanwinchester closed 2 weeks ago
Huh, interesting! We took this lib over and I know there was some... funky behavior across some previous versions that got rolled back. Let me take a dive into the code and see if there's a cleaner way of handling this. Having opts
and params
is sort of an antipattern IMO, maybe we can clean this up a bit
Should these be injected in the request phase based on the resource being requested?
No matter what I try, the scope in the url params is always
"openid email profile"
How can I override this to add scopes?
In the docs it says
but if I add that and add scopes it still doesn't change.
I've tried in both
and
As well as every other wording or combination I can think of...