...
- (IN PROGRESS) Move advanced options to each section (if applicable)
- (DONE) Make sure advanced is last (currently failsafe is last)
- (DONE) Defaults for CRUD at object level
- Insert/Update/Select groups
- Delete groups that Grouper created
- Insert/Update/Select entities
- Delete entities that Grouper created
- Insert/Update/Select memberships
- Delete memberships that Grouper created
- (IN PROGRESS) Defaults for CRUD at attribute level
- If the object selects, the attribute selects
- If the object inserts, the attribute inserts
- If the object updates, the attribute updates
- (DONE)There is no concept of field anymore, only attribute
- (DONE)The notation (e.g.) grouperProvisioningGroup.name will still be supported
- Multiple matching/search attributes, prioritized
- Dao can search for all at once or each at a time, the input will specify the search attribute(s)
- Matching and search attributes will be configured after attributes are configured
- Pick how many, select each one with drop down
- Validations will have an opening option as to whether validations are customized (dont show by default)
- (DONE) LDAP DN is not an attribute: ldap_dn (instead of field name)
- LDAP automatic settings will show the setting and ask if should be customized (e.g. DN)
- LDAP DN should be based on RDN
- (DONE) groupToId2 etc will just be named groupAttributeValueCache0-3
- Can be configured below attributes in the groupLink section
- (DONE) Refactor entity attribute resolver config
- Configs should have a hierarchical prefix on the config suffix
- FROM provisioner.genericProvisioner.sqlConfigId to provisioner.genericProvisioner.entityResolver.sqlConfigId
- Easy way to massage characters
- How many character substitutions
- Substitute a regex (or lack of regex)
- For a string
- Which objects / attributes to apply to
- (DONE) Multi-valued attributes are "sets" and not "arrays"
- (DONE) Rename classes and methods to be consistent (e.g. FROM retrieveGrouperTranslator TO retrieveGrouperProvisioningTranslator)
- (DONE) Adjust defaults to make sense or rename configs so the default is intended. e.g. retrieve all entities in full sync should default to true
- Upgrade step for that???
- Screen should flow from top to bottom. You shouldnt need to scroll up to see an option of configure an option
- (DONE) Sources to provision should be in the entity section
- Translate from object or sync object in one fell swoop
- Add indent level to json metadata and indent on screen