Remove reliance on x5c
property at /jwks
#2716
Labels
tooling
Tooling, automation and CI to support development.
x5c
property at /jwks
#2716
The staging
/jwks
endpoint: https://te-auth.id.tbs-sct.gc.ca/oxauth/restv1/jwksSuccess criteria: Finding another way to check token sigs without using
5xc
property.This would allow us to take a step toward replacing our custom auth app (for local development and CI) with one of the more turn-key mock oauth2 server.
I recommend we remove our usage of the poorly supported (as per a few mock oauth server projects) and unadvised (as per Google Engineering and also in-practice in their infra) openid feature (the
x5c
property).Benefits
This would allow us to more easily benefit from migrating to a mock oauth2 server (for local development and CI). Migrating to a mock server would allow us to abandon our own
auth
app, and the special-case auth code paths withinapi
app.Relevant code
Where we process the
x5c
property into a config object we use to later check token sigs:gc-digital-talent/api/app/Services/OpenIdBearerTokenService.php
Lines 74 to 80 in 13ae7e3
Email from Doug Harris of SiC:
Added this to icebox for now. cc @tristan-orourke
The text was updated successfully, but these errors were encountered: