Hi Anton - I have noticed this behavior as well when using the Local Network UDC. Myself and others will attempt to investigate this and get back to you about it. It seems that the recommended approach is to use the WORKGROUP domain / group name instead of the local server name - IF you inttend to use the UDC with LOCAL Network. You can then delete the duplicate users with the computer name entry. It does not seem there is a way to update the User Directory connector entry property for the user using the QMC.
Also so you are aware, there is a known issue where the Local Network UDC does not recognize or pull in the windows group value - which normally could be used as the group parameter when defining an access rule to lock user access down using specific groups.
In regards to assigning access passes - you can create a simple security rule (user access rule) for the user access passes and assign a value such as like * - this will allow ALL created users in the Windows operating system access to the hub. I know, it would be ideal if you used the window group parameter like you can do with Active Directory UDC (as seen in the video) but the Local Network UDC does not have that yet.
What you can do is create a custom property for the user resource, assign some values such as departments / groups. Then for each user in the users list that you want to have access to the HUB - assign that custom property to them.
Then in the user access rule - use that custom property value and it will lock down user access to the hub and only allow those users.
here are some screen shots that can help.
Simple rule for ALL users to have access
Custom Property - created to lock down access to values YOU assign to the property
Make sure Users resource is selected
Assigning the user the custom property value
Create rule for the user access (available in the tokens and licensing section)
Hope this helps
let us know
I appreciate your quick respond. Glad to hear that it's not that I'm doing it wrong
I assume this would be available in the future release? I understand this is an edge case, because most users would be connected to the domain instead of local server (I'm using it for testing anyway, thus using local server for now). Let me tinker a bit more and let you know if/when I have further questions.
I have a similar issue. I created local users on the server and then created a "local network" UDC (and of course I assigned them licenses).
My users now appears as belonging to "WORKGROUP" domain.
I am not able to log in with any of these users on the hub. I tried with "WORKGROUP\<user>", "<server_name>\user", and "<user>". Qlik Sense doesn't recognize them.
Could you explain your answer "the recommended approach is to use the WORKGROUP domain / group name instead of the local server name - IF you inttend to use the UDC with LOCAL Network."?
Thanks a lot
I am told this is a bug and should be fixed in a service release, available shortly.
- I would recommend going into the QMC and delete those users
- access the URL for the hub
- log in with the user id that is local to the machine - format: user NOT workgroup\user
- - you will get a message that the access pass needs to be assigned
- assign the access pass for the user
- you should be able to log in again.
let us know
I'm not sure if I am having the same issue. I'm running Sense 1.1.
I've posted a question over here:
Any thoughts you have will be greatly appreciated.