Dynamic jwks url by discovery document #417

[mabuonomo]

Hi, this PR is linked to issue #417

[joshcanhelp]

Thank you for the contribution!

I have 2 important changes here. Also, please revert your whitespace changes here, as it makes it difficult to review what has actually changed. Also please use the PR template that is provided.

[mabuonomo]

@joshcanhelp the whitespaces are added/removed by the command "phpcbf", if you want I can restore them.
NB. Also phpcs has many errors

[joshcanhelp]

For this project, use composer phpcbf to load our PHPCS config file. This is on master:

~/Sites/php-auth0/auth0 master
❯ composer phpcbf
> "vendor/bin/phpcbf"
................................................ 48 / 48 (100%)

No fixable errors were found

PHPCS definitely needs some work here but that should happen in different PR, not this one.

[mabuonomo]

For this project, use composer phpcbf to load our PHPCS config file. This is on master:

~/Sites/php-auth0/auth0 master
❯ composer phpcbf
> "vendor/bin/phpcbf"
................................................ 48 / 48 (100%)

No fixable errors were found

PHPCS definitely needs some work here but that should happen in different PR, not this one.

same result on my branch, maybe phpcbf not fix (and check) the spaces.
I've reverted spaces

[joshcanhelp]

@mabuonomo - Sorry but can you revert all the style and naming changes in this PR? Most of the changes here are noise and renaming requestJwks -> request is a breaking change for anyone extending that class.

I would suggest adding a new class for the discovery doc (aka issuer) as that information can be used in a number of different places, not just for the JWKS.

[joshcanhelp]

@mabuonomo - Just FYI ... we're doing some work with the JWKS fetching in #426 that should address your custom JWKS issue. We'll add discovery at some point but that will probably come with a new Auth0 login helper class.

[joshcanhelp]

Addressed in #426

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.