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

Import of policies should import application and resource type information as well


    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 12.0.0
    • Fix Version/s: 14.0.0
    • Component/s: policy editor
    • Environment:
      OpenAM 12.0.0
    • Sprint:
      Sprint 104 - Team Curie, Sprint 105 - Team Curie, Sprint 106 - Team Curie
    • Epic Link:
    • Support Ticket IDs:


      If you export policies from Server A, and then immediately try to import the policies into Server B - it will fail if Server B doesn't contain the Application names that contained the policies from Server A.

      The expectation from the customer is that they can export their policies, and then make no changes and import the policies to another server – the import process should create the correct Application names if needed.

      The current behavior is that the import fails, because the application names listed in the XACML file do not exist on the other server.

      This also occurs when they export from one realm, and try to import the policies into a different sub ream- because the application names do not exist in the sub realm.

      Note that resource types must also be exported and imported. See comments below and bug OPENAM-6972 referenced below.


          Issue Links



              • Assignee:
                jaco.jooste Jaco Jooste
                matthew.miller@forgerock.com Matt Miller [X] (Inactive)
                QA Assignee:
              • Votes:
                1 Vote for this issue
                10 Start watching this issue


                • Created: