Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auth: support providing custom certificate URLs #11005

Closed
idhame opened this issue Oct 18, 2024 · 1 comment
Closed

auth: support providing custom certificate URLs #11005

idhame opened this issue Oct 18, 2024 · 1 comment
Assignees
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@idhame
Copy link
Contributor

idhame commented Oct 18, 2024

This feature has been requested before in googleapis/google-api-go-client#640

The current documentation for Google Chat bot verification shows

If the Authentication Audience field of the Chat app connection setting is set to Project Number, the bearer authorization token in the request is a self-signed JSON Web Token (JWT), issued and signed by [email protected]. The audience field is set to the Google Cloud project number that you used to build your Chat app. For example, if your Chat app's Cloud project number is 1234567890, then the audience field in the JWT is 1234567890.

In their code examples they show that the url to get the certs for validation should be https://www.googleapis.com/service_accounts/v1/metadata/x509/[email protected]

As of now the auth package doesn't support the kind of JWT validation specified in the docs.

@idhame idhame added the triage me I really want to be triaged. label Oct 18, 2024
@quartzmo quartzmo added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed triage me I really want to be triaged. labels Oct 18, 2024
@idhame
Copy link
Contributor Author

idhame commented Nov 10, 2024

hi @quartzmo, can you review my PR #11006 related to this feature request ? thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants