django cloud run custom domain redirecting to login - django

During development I an able to login and logout just fine. I have deployed the Django app to Google cloud run. I am also able to login with the Service URL which has the syntax https://example-service-xxxxxxx-ey.a.run.app.
Furthermore, I have also connected a custom domain via Firebase to the cloud run service and everything works well apart when I signin in which case I am redirected back to the login page.

Related

How to call google cloud shell from Postman or different browser

I created a node.js sever inside the cloud shell. I can open the Web Preview and it will send a GET request to my server, but I also want to send a POST request to the server. If I try to call the same USL provided in Web Preview from anywhere outside of the current broswer which I am looged in with my google cloud, I will be redirected to login page.
Is there a way to Authenticate to google cloud by adding hedears in an API request?
To generate a token so that you can authenticate to google cloud follow the below steps:
Login to Google Cloud Console
In API & Services -> Credentials create an OAuth 2.0 client ID
Authorize the redirect URL
Login to Postman client/browser app
Use the settings mentioned in the document in the postman.

Is it possible to change the gcloud sdk's oauth app?

I am using gcloud auth login + container clusters get-credentials to e.g. fetch credentials for a kubernetes installation. This works great ;).
But whenever gcloud auth login is called a oauth browser is shown, which presents:
That's ok! I was wondering if it's possible to change the oauth app used in this screen from "google cloud sdk" to a company wide application? E.g. we have a OAuth Enabled Google Project and I would like my co workers to „allow“ this app and not the generic „google cloud sdk“.
PS: I am aware of the fact that there are service accounts for headless login -> but I want the user to authenticate personally
This screen doesn't belong to "google cloud sdk" app, it's part of OAuth2 flow. Here it's the explicit permissions flow: It ask the user to consent the permissions to the app (name "client" in the OAuth doc).
So, here it's the Google identity provider which present this page. And you can't customize it.

Is there a way to configure an external SSO login system with my existing Django Web Application

I have a django application with a default login configured. I also have an external SSO login system. Need to configure the django application so that it can use the SSO and login to the application.
AWS Cognito tool allows you to sync your mobile app with web app. You can easily manage your application users as an administrator.

Gapps script: using user auth credentials to authorize vs external django app service (which uses google as oauth provider)

The workflow I need:
User authenticated via google to a g-apps spreadsheet with google-apps-script.
The script then calls an external service( a django app) which uses oauth for login with google backend - and authenticates with the user google credentials.
Searched from the G-apps api docs but couldn't find how to utlizlize the use existing google login to authenticate vs an external service also using google oauth login (there are docs to connecting to a google api, but that's a different use case)
Is this even possible? if so - How can I access the user credentials directly or preferably allow UrlFetchApp to use the credentials transparently.
Maybe my google foo is failing me, but I can't find examples/explanations for this scenario.

Authenticating embedded Kibana iframe with AWS Cognito

I have a web app which already uses AWS Cognito to authenticate my users. These users have been granted role-based access to the Kibana URL of my AWS ElasticSearch cluster. But when I provided an embedded kibana dashboard iframe into my user's session, it doesn't work. I think I need to pass the Cognito session information along with the iframe. Is there a way to pass the Cognito session information along with the iframe? The embedded dashboard starts working when I login to Kibana in a separate browser tab, which leads me to believe this is an authentication issue. Any pointers will be of great help! Thanks.