[
https://issues.apache.org/jira/browse/SYNCOPE-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1888:
--------------------------------------------
Fix Version/s: 3.0.13
Affects Version/s: 3.0.12
> Console: change required property for specific inputs in policy configuration
> -----------------------------------------------------------------------------
>
> Key: SYNCOPE-1888
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1888
> Project: Syncope
> Issue Type: Bug
> Components: console
> Affects Versions: 3.0.12, 4.0.0
> Reporter: Alberto Bogi
> Priority: Major
> Fix For: 3.0.13, 4.1.0, 4.0.1
>
>
> During the configuration of policies through the Syncope console, it's been
> identified the following issues that lead to errors under specific conditions:
> *Account Policy*:
> If "Max Authentication Attempts" field is left empty, submit form for save
> policy changes goes on error. This happens because the field requires a
> non-null integer. Currently, there is no way to set the value to 0 to
> indicate that no maximum attempt check should be enforced by the policy.
> *Password Policy*:
> If the "History Length" field is left empty, the form submission fails due to
> the same reason, i.e field expects a non-null integer. Similarly, there is
> no option to set it to 0 to indicate that no history length control should be
> applied.
> *Propagation Policy*:
> If the "Max Attempts" field is left empty, an error occurs because the field
> is required to contain a non-null integer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
