Check illegal fallback usernames

Answered Question
Feb 11th, 2010

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

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 6 years 9 months ago

Chances are the bad username has a different number of characters that the good username.  Try this:

+ [#username fallbackusername .*#]

- [#username (?!fallbackusername)\b.*#]

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Fri, 02/12/2010 - 13:33

Try:

+ [#username fallbackusername .*#]

- [#username (?!fallbackusername) .*#]

Where fallbackusername is the desired fallback username.

ltenbrink Mon, 02/15/2010 - 23:17

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

Correct Answer
Joe Clarke Mon, 02/15/2010 - 23:44

Chances are the bad username has a different number of characters that the good username.  Try this:

+ [#username fallbackusername .*#]

- [#username (?!fallbackusername)\b.*#]

ltenbrink Mon, 02/15/2010 - 23:55

Hi Joe Marcus,

This does the trick.

Thanks again, you really helped us out.

Laurence.

Actions

This Discussion