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

Node Schema Required Array Shouldn't Include Fields with Default Values

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Do
    • Affects Version/s: 7.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      A call to https://default.iam.example.com/am/json/realms/root/realm-config/authentication/authenticationtrees/nodes/LdapDecisionNode?_action=schema currently gives back an object that contains an array of the required fields attached to that node. As it turns out, a number of these fields already have default values on the backend, and thus do not return an error if they are left blank on save. To prevent confusion, and to ensure the front end can display validation on these fields accurately, we should remove any field that has a default value from the required array. 

       

      Example: The call above has the below array of required fields returned. However, the values for searchScope, ldapConnectionMode, userCreationAttrs, and heartbeatTimeUnit all have default values on the backend, and can be left blank on save. These fields should not be sent in the array of required fields.

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

       

      Acceptance Criteria:

      Backend fields that have default values are not returned in required array from schema call in nodes

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: