Problem with ./client script after adding users to users.properties

[przemyslawcyprys]

Hello,

We've encountered issue with access to running Fuse 6.3 instance by usage of ./client.

1. In users.properties file we have only admin user and pass

admin = password,admin

2. Fuse is running in foreground so I'm using ./client

]$ ./client
Logging in as admin

3. Success.. but....

4. In users.properties (manually added to file or via jaas module in Karaf) we're creating new roles, users and groups so it's look like that

admin = password,admin
_g_\:GROUP_E = group,ROLE_1
_g_\:GROUP_D = group,ROLE_2
_g_\:GROUP_C = group,ROLE_4
_g_\:GROUP_B = group,ROLE_3
_g_\:GROUP_A = group,ROLE_5
user1 = passuser1,_g_:GROUP_E
user2 = passuser2,_g_:GROUP_C
user3 = passuser3,_g_:GROUP_D
user4 = passuser4,_g_:GROUP_A
user5 = passuser5,_g_:GROUP_B

5. Running ./client works now differently...

]$ ./client
Logging in as user3

Why it's logging as user3, not admin? If I'm removing the user 3 definition, ./client is trying to log as for ex. user4.

Thanks for help and hints in advice

[grgrzybek]

Hello

This is just implementation feature. org.apache.karaf.client.Main class (which is used by bin/client script) is loading users.properties to java.util.Properties object - which is backed by (unsorted) Hashtable. And simply first non-group user is used as the one to be logged with.

It can be simply fixed by using LinkedHashMap, but I imagine it's better to explicitly specify "bin/client -u <user>" option.

regards

Grzegorz Grzybek

[davsclaus]

Well spotted Grzegorz.

I think maybe its worth logging a KARAF ticket so they can improve this in a future release. Makes sense IMHO to always load those lines in order.

[grgrzybek]

Hell

Good idea - track the issue here: https://issues.apache.org/jira/browse/KARAF-5017.

regards

Grzegorz