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

Amster doesn't export custom authentication node configuration

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 14.5.0, 5.5.1
    • Fix Version/s: None
    • Component/s: Amster
    • Labels:
    • Support Ticket IDs:

      Description

      Bug description

      Amster export-config does not export configuration details of any custom (ie, non-shipping) authentication nodes. A subsequent import of the exported configuration will fail to correctly create the custom auth nodes.

      Steps outlining how to recreate the issue:

      1. Create/Install a custom authentication node
      2. Configure an authentication tree containing the custom node
      3. Use amster export-config to dump the config to files
      4. Import the config on a clean AM instance
      5. Observe that the authentication tree object exists, but cannot be viewed/edited in the admin UI.
      Work around

      Authentication node config can be manually added via REST before or after the amster import-config in order to fix the tree.

      PUT /json/realms/root/realm-config/authentication/authenticationtrees/nodes/mynodetype<uuid>
      {config ...}
      

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jon.knight@forgerock.com Jon Knight
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: