[OPENAM-12233] Amster doesn't export custom authentication node configuration Created: 18/Dec/17  Updated: 14/Nov/18  Resolved: 16/Jul/18

Status: Resolved
Project: OpenAM
Component/s: Amster
Affects Version/s: 14.5.0, 5.5.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jon Knight Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: AME
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by OPENAM-13157 Custom Authentication Nodes not being... Resolved
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 ...}

 



 Comments   
Comment by Phill Cunnington [ 04/Apr/18 ]

Moving issues to the "backlog" that do not have a customer ticket attached.

Generated at Mon Sep 21 16:50:07 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.