Hi channel! We just updated our DataHub instance ...
# troubleshoot
h
Hi channel! We just updated our DataHub instance to v0.8.44 and found this behavior: we cannot see new users or policies anymore. These are the steps that we are following: 1. We generate an invite link as in previous months. 2. New users use it to register. 3. Then they notify me so I can assign them a group. Groups have associated policies. 4. I cannot find new users in the user list. Old users are there, but none of the new ones appear. 5. They can login into the platform, but receive a "unauthorized" page, as by defautl they have no access rights. 6. If I activate some "all users" policy, already existing but Inactive, they can access everythin. 7. Still cannot see them in user list. 8. I try to create a new policy a bit more restrictive than the default one, but after successfully creating it, it never appears in the list. Has anyone experienced something similar? Could you fix it? Thanks!
b
Taking a look now..
I have not heard about this yet. Let us try to recreate this on our side (cc @echoing-airport-49548)
e
Hey @hallowed-dog-79615 I just tried to reproduce this issue. I invited a new user, signed up, and I didn’t see an authorized page. I’m also able to see the user in the user list
To verify, did you create the new policy through the UI?
I know this also doesn’t exactly answer your question, but are you familiar with the new Roles feature at all?
h
Hi @echoing-airport-49548 and @big-carpet-38439! The issue here is not that they receive an unauthorized page. That's normal, as we set this policy when our instance was working properly. The real issue is new users nor new policies not being listed although they are there in the database, as they can login. I am familiar with new roles, yeah! Indeed, that's another part of the issue: as I said, I can see old users, the list has become "frozen" in the pre-v0.8.44 state. So, if I try to give this old users a role, I get a "role applied successfully" message. But then if I refresh, roles have been reset to "none". It seems our instance is not refreshing things according to new entries in the database, or something like that. Wanted to know if anyone did experience this since last version in order to clarify if its on update's side or our side! Thanks!