Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-14373

custom Identity Repository (IdRepo) implemenations can not be configured via AM console or REST

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.5.0, 6.0.0.6, 6.5.0.1
    • Fix Version/s: None
    • Component/s: console, rest, REST-SMS
    • Labels:
      None
    • Environment:
      Oracle JDK 1.8.0_151-b12
      Apache Tomcat/9.0.8
      AM 6.5.0
    • Support Ticket IDs:

      Description

      Bug description

      Instances of custom Identity Repository implementation can not managed via AM console or REST calls

      How to reproduce the issue

      1. Configure AM
      2. Build custom Identity Repository as described in https://backstage.forgerock.com/docs/am/6.5/maintenance-guide/#customizing-data-stores
      3. Log into AM console
      4. Configure an instance of the custom Identity Repository
      Expected behaviour
      As in previous versions it should be possible to configure custom Identity Repositories via AM console.
      
      Current behaviour
      Instances of a custom Identity Repository can not be configured via AM console.
      

      Work around

      use deprecated ssoadm datastore sub-tasks

      Analysis

      The docs are missing the following important information

      Excerpt from SubSchema
      <SubSchema i18nKey="x4000" inheritance="multiple" maintainPriority="no"
                 name="CustomRepo" supportsApplicableOrganization="no" validate="yes">
      

      Create a file CustomRepo.section.properties (the prefix must be the name of the SubSchema).

      in this file, map the AttributeSchemas to a section

      e.g.

      excerpt from SubSchema
          <AttributeSchema name="sunIdRepoClass"
                           type = "single"
                           syntax = "string"
                           any="required"
                           validator="RequiredValueValidator"
                           i18nKey = "a2013">
              <DefaultValues>
                  <Value>FULL_QUALIFIED_CLASSNAME</Value>
              </DefaultValues>
          </AttributeSchema>
      
      excerpt from CustomRepo.section.properties
      pluginconfig=sunIdRepoClass
      

      As an example, look at file LDAPv3ForOpenDS.section.properties which can be found in WEB-INF/classes of AM web-application.

      Bundle CustomRepo.section.properties into AM web-application so it can be loaded by the WebApp classloader (e.g. package it into WEB-INF/classes)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bthalmayr Bernhard Thalmayr
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated: