Assigned
Status Update
No update yet.
Comments
di...@google.com
Hello,
Thank you for reaching out to us!
I tried to reproduce this issue at my end. However, I am getting the intended behavior.
Please check the
Please let me know if that helped you with your use case and if there is anything else you would need assistance with.
Thank you
di...@google.com
di...@google.com
jo...@pantheon.io
Hi, please read the documentation you linked:
> Scheme
> JavaScript origins must use the HTTPS scheme, not plain HTTP. Localhost URIs (including localhost IP address URIs) are exempt from this rule.
Subdomains of localhost (ie. foo.localhost) *are* "Localhost URIs" but are not currently exempt from the rule, contrary to the documentation.
> Scheme
> JavaScript origins must use the HTTPS scheme, not plain HTTP. Localhost URIs (including localhost IP address URIs) are exempt from this rule.
Subdomains of localhost (ie. foo.localhost) *are* "Localhost URIs" but are not currently exempt from the rule, contrary to the documentation.
Description
This will create a feature request which anybody can view and comment on.
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish: The customer wants the API gateway to support the mTLS authentication method. Current authentication methods do not support the mTLS methods [1,2]
How this might work: Attached the sample diagram of the flow. The flow will have some APIs in Cloud Run and Cloud Function. But, some requests will also have to reach GKE. So the API gateway needs to support the mTLS authentication.
If applicable, reasons why alternative solutions are not sufficient: Authentication methods with GKE services are limited.
Other information (workarounds you have tried, documentation consulted, etc):