02-11-2010 11:27 PM
Hello,
I want to make sure that only one fallback user is configured in our devices. With RME Compliancy managemen I would like to check if any other fallback usernames are configured then our standard fallback user. I assume that it should be something like:
- username [#!fallbackusername .*]or
- [#!username fallbackusername .*#]
But these doesn't do the trick.
The problem is that it's a negative rule (should not exsist), and the default username we use must be negated (other than fallbackusername). Besides that, the rule contains wildcards because passwords are encrypted, and thus random in devices.
Does anyone have any ideas?
Thanks very much.
Laurence
Solved! Go to Solution.
02-15-2010 11:44 PM
Chances are the bad username has a different number of characters that the good username. Try this:
+ [#username fallbackusername .*#]
- [#username (?!fallbackusername)\b.*#]
02-12-2010 01:33 PM
Try:
+ [#username fallbackusername .*#]
- [#username (?!fallbackusername) .*#]
Where fallbackusername is the desired fallback username.
02-15-2010 11:17 PM
Hi Joe Marcus,
Thanks for your response.
I have a device configured with two username, one like "fallbackusername" and one other user. The compliancy check with the statement you suggested show that the device is compliant, where i expected the device not being compliant because another username exsist.
Any other suggestions?
Thanks.
Laurence
02-15-2010 11:44 PM
Chances are the bad username has a different number of characters that the good username. Try this:
+ [#username fallbackusername .*#]
- [#username (?!fallbackusername)\b.*#]
02-15-2010 11:55 PM
Hi Joe Marcus,
This does the trick.
Thanks again, you really helped us out.
Laurence.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide