[BUG] Enforced "max login attempts" blocks EE creation

[benoiton]

On a fresh install of EJBCA 9.1.1 Community:

• Create a new EE profile name "zz"
• Only change "Maximum number of failed login attempts" => Use, Default=3, NOT unlimited, NOT modifiable
• Create a new EE on profile "zz"
• Fill the fields and press "Add" => OK
• Rename the EE profile "aa"
• Create a new EE, don't touch the profile selector and let it on "aa" profile
• The "Maximum number of failed login attempts" is on "Specified" with an empty text field
• Fill the fields and press "Add" => Error "Max failed logins is not modifiable."
• Switch to "EMPTY" profile and switch back to "aa"
• The "Maximum number of failed login attempts" is on "Specified" with "3" in text field
• Fill the fields and press "Add" => OK

In other words, the alphabetically first EE profile cannot be directly used if the number of failed login attempts is limited and not-modifiable. If there is 2 available profiles, switching to another profile et switching back makes it work.

[primetomas]

I don't think you have to rename the profile. When you click add and it selects the first profile in the list, if that profile have the settings for failed login attempts you see it directly when you enter "add end entity". Am I correct with that? (Assuming It's the Admin UI).

[primetomas]

hi @benoiton I've identified the issue. The number value in the backing bean is only read on a "change" event, not on initialize. We have a fix for this that will be released in EJBCA 9.5.

Thanks for the report!