Config uses jwt assertions over client_secret for oauth2 authentication of the application. This implementation was made specifically for Azure AD. https://learn.microsoft.com/en-us/azure/active-directory/develop/certificate-credentials However this does mostly follow the standard. We can general
| 33 | // |
| 34 | // https://datatracker.ietf.org/doc/html/rfc7523 |
| 35 | type Config struct { |
| 36 | cfg promoauth.OAuth2Config |
| 37 | |
| 38 | // These values should match those provided in the oauth2.Config. |
| 39 | // Because the inner config is an interface, we need to duplicate these |
| 40 | // values here. |
| 41 | scopes []string |
| 42 | clientID string |
| 43 | tokenURL string |
| 44 | |
| 45 | // ClientSecret is the private key of the PKI cert. |
| 46 | // Azure AD only supports RS256 signing algorithm. |
| 47 | clientKey *rsa.PrivateKey |
| 48 | // Base64url-encoded SHA-1 thumbprint of the X.509 certificate's DER encoding. |
| 49 | // This is specific to Azure AD |
| 50 | x5t string |
| 51 | } |
| 52 | |
| 53 | type ConfigParams struct { |
| 54 | ClientID string |
nothing calls this directly
no outgoing calls
no test coverage detected