Closed yu-iskw closed 1 year ago
We can protect self-hosted metabase on Google Cloud Kubernetes Engine with Google Cloud IAP. When we call REST APIs through Cloud IAP, we need to add a ID token with the Authorization header.
Authorization
https://cloud.google.com/iap/docs/authentication-howto
curl --verbose --header 'Authorization: Bearer ID_TOKEN' URL
NA
provider "metabase" { host = local.metabase_credentials["host"] username = local.metabase_credentials["username"] password = local.metabase_credentials["password"] headers = { Authorizer = "Bearer: ${var.id_token}" } }
Hi @yu-iskw, thanks for raising the suggestion! Very much in favour of this - I'll take a look as soon as I can 🙂
Description
We can protect self-hosted metabase on Google Cloud Kubernetes Engine with Google Cloud IAP. When we call REST APIs through Cloud IAP, we need to add a ID token with the
Authorization
header.https://cloud.google.com/iap/docs/authentication-howto
New or Affected Resource(s)
NA
Potential Terraform Configuration
References