https://datahubproject.io logo
Join Slack
Powered by
I was reading through <https://datahubproject.io/d...
# troubleshoot
s
I was reading through https://datahubproject.io/docs/policies/ and noticed it does not mentioned where we can set the default user with admin rights in case we are using OIDC. What property can be used to set the user when using OIDC?
@big-carpet-38439 @mammoth-bear-12532 Any suggestions?
b
@square-activity-64562 Right - so you'll need to change the policies.json file directly to set another default user!
Good catch on the docs, we should update to reflect this. Alternatively, you can keep JAAS enabled (which we'd recommend) and keep "datahub" as the admin user
(so you never get locked out)
s
where can I find this 
policies.json
file? And how would I use 
datahub
user to login when using OIDC?
But when using OIDC how can I login using datahub?
b
You cannot, you must go to <datahub-url>/login and login with "datahub" user in order to log in as this user
Thus, JAAS must be enabled (is by default)
The other option is to change policies.json file you've shown above to add policies for some other root user that will login via OIDC (such as yourself)
s
These policies MCE have editable false. Does this mean we cannot go and edit these once they are ingested? Obviously we can go into database and delete these. I was just thinking that instead of editing these (which will require making a new docker image) can I ingest the required MCE after installing it? With the latest version (with policies) will metadata-ingestion need token to ingest data? If a token is required where can I generate the token? If not, isn't that a security issue if metadata-ingestion can be done without auth which basically allows us to do anything? https://datahubspace.slack.com/archives/C029A3M079U/p1630998362090300
Open in Slack
PreviousNext
Powered by