Isilon usermapper rule with wildcard is not working
Hi All,
I have NIS & AD configured in my isilon, for the multi-protocol environment I am trying the change the AD user primary group from "domain users" to that of the primary group from his/her unix account.
So the usermapper rule for this is '*\* += * [group]', but this is not working. The AD user access token is still showing "domain users" as the primary group.
Where as if I create a rule specific to any single user like '*\user01 += user01 [group]' it is working just as expected.
Has anyone experienced this issue? If so how was it resolved?
I would suggest be explicit with user mapping rules, I cannot find anywhere that states wildcards are supported/unsupported anywhere but I did have an issue with one of my customers where we were using mapping rules that were not explicitly correct both in syntax and naming convention and it appeared to take and create the rule but did not correctly apply the rule to the desired user.
The end result was to ensure that our usernames and groups were explicitly correct as I understand user mapping does not do any username validation so I would expect this to be part of your problem.
are you able to validate if you call the names directly/correctly does it apply the mapping rules as expected?
Page 26 gives some examples how wildcards can be applied, and what will NOT work.
Your case '*\* += * [group]', is not exactly covered -- but most likely the mapper cannot make sense of finding two wildcards on the left side and only one on the right side. Try:
abhilas945
11 Posts
1670
1
Posted June 29th, 2016 06:00
finally! I got the solution few days back from the support.
My NIS users have first letter in uppercase!, normalization is already enabled for AD users and somehow it is not enabled for NIS users.
The below command has normalized the NIS users & groups, after this point the usermapper rules started working.
isi auth nis modify --normalize-groups=1 --normalize-users=1