Describe the bug
When running the datahub helm chart v0.10.0, the default account datahub:datahub is not created as an admin user. When logging in as datahub user.
On logging in the following is shown from datahub-frontend, clicking on Settings -> Only shows the following options
On logging in the following is shown from datahub-frontend, clicking on My Profile -> Shows unauthorized
All Components are successfully deployed, currently datahub-frontend, datahub-gms and datahub-actions + pre-installers/setup
Datahub-frontend logs
2023-03-01 13:01:22,853 [application-akka.actor.default-dispatcher-14] ERROR controllers.TrackingController - Failed to emit product analytics event. actor: urn:li:corpuser:datahub, event: {"title":"DataHub","url":"https://edgeai-datahub.nss.vzwnet.com/user/urn:li:corpuser:datahub","path":"/user/urn:li:corpuser:datahub","hash":"","search":"","width":1280,"height":587,"prevPathname":"/","type":"PageViewEvent","actorUrn":"urn:li:corpuser:datahub","timestamp":1677675647877,"date":"Wed Mar 01 2023 08:00:47 GMT-0500 (Eastern Standard Time)","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36","browserId":"f727face-172b-4add-b2b9-e5b618f023d7"}
2023-03-01 13:56:34,337 [application-akka.actor.default-dispatcher-4] ERROR o.p.o.p.creator.OidcProfileCreator - Bad User Info response, error=null
2023-03-02 05:26:05,111 [application-akka.actor.default-dispatcher-13] ERROR o.p.o.p.creator.OidcProfileCreator - Bad User Info response, error=null
Datahub-gms logs
2023-03-02 07:01:59,544 [I/O dispatcher 1] INFO c.l.m.s.e.update.BulkListener:47 - Successfully fed bulk request. Number of events: 1 Took time ms: -1
2023-03-02 07:02:01,940 [ForkJoinPool.commonPool-worker-13] WARN org.elasticsearch.client.RestClient:65 - request [HEAD https://edgeai-elastic.nss.vzwnet.com:443/datahub_usage_event?ignore_throttled=false&ignore_unavailable=false&expand_wildcards=open%2Cclosed&allow_no_indices=false] returned 1 warnings: [299 Elasticsearch-7.17.6-f65e9d338dc1d07b642e14a27f338990148ee5b6 "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
2023-03-02 07:02:04,081 [ForkJoinPool.commonPool-worker-23] WARN org.elasticsearch.client.RestClient:65 - request [HEAD https://edgeai-elastic.nss.vzwnet.com:443/datahub_usage_event?ignore_throttled=false&ignore_unavailable=false&expand_wildcards=open%2Cclosed&allow_no_indices=false] returned 1 warnings: [299 Elasticsearch-7.17.6-f65e9d338dc1d07b642e14a27f338990148ee5b6 "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
2023-03-02 07:02:04,156 [ForkJoinPool.commonPool-worker-23] WARN org.elasticsearch.client.RestClient:65 - request [POST https://edgeai-elastic.nss.vzwnet.com:443/datahub_usage_event/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true] returned 1 warnings: [299 Elasticsearch-7.17.6-f65e9d338dc1d07b642e14a27f338990148ee5b6 "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
2023-03-02 07:03:40,335 [pool-11-thread-1] WARN org.elasticsearch.client.RestClient:65 - request [POST https://edgeai-elastic.nss.vzwnet.com:443/datahubpolicyindex_v2/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true] returned 1 warnings: [299 Elasticsearch-7.17.6-f65e9d338dc1d07b642e14a27f338990148ee5b6 "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
To Reproduce
Steps to reproduce the behavior:
Install datahub helm chart for 0.10.0
login as datahub:datahub
Go to settings (see above image)
Try to access profile and get unauthorized
Expected behavior
The expected behavior is when going to settings > it should show administrative options in the UI for managing/creating users and additional items.
Screenshots
Added Screenshots above
Desktop (please complete the following information):
Bowser Google Chrome
Additional context
Installed with OIDC, however even without OIDC configured the same issue still occurs.
Describe the bug When running the datahub helm chart v0.10.0, the default account datahub:datahub is not created as an admin user. When logging in as datahub user.
On logging in the following is shown from datahub-frontend, clicking on Settings -> Only shows the following options
On logging in the following is shown from datahub-frontend, clicking on My Profile -> Shows unauthorized
All Components are successfully deployed, currently datahub-frontend, datahub-gms and datahub-actions + pre-installers/setup
Datahub-frontend logs
Datahub-gms logs
To Reproduce Steps to reproduce the behavior:
Expected behavior The expected behavior is when going to settings > it should show administrative options in the UI for managing/creating users and additional items.
Screenshots Added Screenshots above
Desktop (please complete the following information): Bowser Google Chrome
Additional context Installed with OIDC, however even without OIDC configured the same issue still occurs.