This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

Cloud run use case

Posted on 10-24-2024 11:16 AM
Aidap
Bronze 3
Bronze 3
Reply posted on --/--/---- --:-- AM

Hello 

We have this use case in which we won't use Google Gmail/ pass to authenticate our users so they can access our applications internally and externally. Still, right now, we are focusing on internal applications such as our web server, web client, `airflow, etc. Each of these services is hosted on the individual cloud run.

The action we took :

We tried using IAP and added the HTTPS Load Balancer and enabled the IAP, but the downside is that we don't have a custom domain for each of these cloud-run services, so we can't use LB, We are using Firebase UI to authenticate our web server user but this is implemented with our web server source code and hosted with it on the cloud run, so other apps don't use it Now my question is, can we build the one firebase and host on one of the cloud runs and then connect it to other cloud runs to auth the users and redirect it to each cloud run? If so, is there any doc to explain this? I couldn't find any in official Google Docs; if this is not possible at this moment, what else can we do 

0 1 255
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
djs_75
Silver 2
Silver 2
Reply posted on --/--/---- --:-- AM

Why would you do that as opposed to setting up a Workforce Identity pool or configure the Identity service and use that as the invoker to you cloud run? An OIDC claim is easier to manage, and you should be using it to authenticate to the Firebase UI. If you set your OAuth consent and workforce identity pool it'll have the identities to authenticate and all to invoke

0 Likes