III-6410 Cleanup auth0 Code

[JonasVHG]

Changed

• app/RoutingServiceProvider: pemfile will only be the Keycloak one & getManagementTokenProvider() will always be a Keycloak one.
• JsonDocumentFetcherProvider: getTokenGenerator() will always return a KeycloakTokenGenerator
• Authentication/AuthenticateRequest: rename $auth0Down to $oAuthServerDown & $jwtUrl is always set.
• AuthenticateRequestTest: Use KeycloakMetadataGenerator instead of Auth0MetadataGenerator in tests & update MockResponses with Keycloak metadata.

Removed

• Auth0TokenGenerator
• Auth0MetadataGenerator

Related PR

• https://github.com/cultuurnet/appconfig/pull/891

---

Ticket: https://jira.publiq.be/browse/III-6410

[LucWollants]

I think this can also be changed because keycloak will always be enabled

udb3-search-service/src/Http/Authentication/AuthenticateRequest.php

Line 148 in 86e610a

$jwtUrl = $config->get('keycloak.enabled') ? $config->get('jwt.domain') : null;

[LucWollants]

Maybe prepare a config change that removes all the Auth0-related config? However, we need to wait to merge that cleanup of the config until this code is deployed to production.

[JonasVHG]

Maybe prepare a config change that removes all the Auth0-related config? However, we need to wait to merge that cleanup of the config until this code is deployed to production.

Yes, I decided to wait with this task, because as long it is not deployed it cannot be merged. I could also make one with a wait-to-merge-label.

[LucWollants]

Yes, I decided to wait with this task, because as long it is not deployed it cannot be merged. I could also make one with a wait-to-merge-label.

I would already make a pull request, so we can put some "pressure" on releasing everything