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

Cannot expand Type menu in Subjects after manually importing a policyset

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not a defect
    • Affects Version/s: 6.5.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      AM Sustaining Sprint 72, AM Sustaining Sprint 73
    • Story Points:
      3
    • Needs backport:
      No
    • Support Ticket IDs:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      After importing a policyset using Amster and creating manually a policy in that policyset, nothing can be selected in Type drop-down menu in Subjects page of the policy.

      How to reproduce the issue

      Details steps outlining how to recreate the issue (remove this text)

      1. Import a policyset using Amsterimport-config --path /home/support/test.json
      1. Login to AM. Access Realm in which Policy Set was imported.
      2. Go to Authorization - Policy Sets. Click on the imported Policy Set
      3. Add a policy
      4. Click on Subjects - Type field cannot be expanded. Below we can observe an Info: "The "Not..." logical operator can only accept one child"
      Expected behaviour
      Should be able to chose something in Type field.
      Current behaviour
      {...}
      

      Work around

      NA

      Code analysis

      NA

      org.forgerock.$className.java
      ...
      

        Attachments

          Activity

            People

            Assignee:
            lawrence.yarham Lawrence Yarham
            Reporter:
            alex.stan Alexandru Stan [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: