:wave: We enabled google auth on our frontend ins...
# ui
h
πŸ‘‹ We enabled google auth on our frontend instance. We can access our user pages (
/user/urn:li:corpuser:fredrik
) but can’t find ourselves through search. Is this by design?
b
Hi Fredrik -- It's important to note that when you enable auth we do not ingest from your auth source. Instead, we simply enable authentication with your Identity Provider. It's expected that your users already have Metadata profiles within DataHub (via the ingest framework ideally)
So configuring users on DH is currently a 2-step process: 1. Ingest CorpUser "profiles" from your identity provider of choice 2. Configure SSO Authentication with your identity provider
There may be some improvements we can make to this... Like auto-creating the CorpUser entity once someone has logged in...Maybe we can chat about what you'd have in mind
h
Got it! thanks for the explanation!
b
Glad you were able to get the authentication itself configured )
πŸ™‚
h
Good instructions made it trivial to get working πŸ‘
πŸ™Œ 1
b
May I take the chance to clarify: 1. once google auth or any form of auth is enabled, the user needs to login in order to access datahub right? Else it will not let him/her see anything? 2. if there is no Corpuser entity for that logged in user, the user is unable to make edits to the metadata? thanks!
b
Hi @better-orange-49102. 1. Yes 2. Actually today we will treat the logged in user as a user who just doesn't have profile information. Today, they are still free to edit metadata (though restrictions on metadata will be coming with the RBAC initiative on the roadmap)
b
thanks for clarifying John!❀️
b
Anytime πŸ™‚