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

IDM should separate internal data from customer defined data in our ds profiles

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Module - Repository DS
    • Labels:

      Description

      IDM has a single profile for all our DS object classes, ldap attributes, and base entries. There are entries in the profile that are internal to IDM that should not be changed by the customer, but we also have object classes and ldap attributes that the customer should change and define on their own.

      An example of this split is to create one idm-internal profile containing everything except managed entries, and then have another profile called idm-managed that has all the idm sample object classes and ldap attributes fo our default managed objects. The idm-managed profile could then be replaced by customers when they define their own managed objects and schema.

      This is just one example, there might be more than just managed as customer customizable data.

        Attachments

          Activity

            People

            • Assignee:
              brmiller Brendan Miller
              Reporter:
              jason Jason Lemay
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: