Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-14199

Non-required fields are being returned in required array from schema call for nodes

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 7.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Target Version/s:

      Description

      When calling https://default.iam.example.com/am/json/realms/root/realm-config/authentication/authenticationtrees/nodes/LdapDecisionNode?_action=schema there is a field that is returned that should not be required. The field is 'secondaryServers'. Leaving this field blank does not throw an error on save, so this is likely just an error in the function that builds the array of required fields.

       

      Example: The call above has the below array of required fields returned. In this array, we can see "secondaryServers". However, if this field is blank, we can still save, even though the backend does not have a default value for this field.

      ["userCreationAttrs", "accountSearchBaseDn", "primaryServers", "ldapConnectionMode", "adminPassword", "minimumPasswordLength", "adminDn", "secondaryServers", "heartbeatInterval", "userProfileAttribute", "heartbeatTimeUnit", "searchScope", "searchFilterAttributes", "beheraEnabled", "ldapOperationsTimeout", "trustAllServerCertificates", "returnUserDn"]

       

      Acceptance Criteria:

      secondaryServers should not be included in the array of required fields for LDAPDecisionNode

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbranch Jon Branch
                Reporter:
                andrew.hertel Andrew Hertel
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: