Details

    • Sprint:
      2018.16 - Tin
    • Needs backport:
      Yes
    • Support Ticket IDs:
    • Verified Version/s:
    • Needs QA verification:
      Yes
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      Amster export fails with 

      Illegal character in path at index 11: json/users/{user}/devices/2fa/webauthn?_queryFilter=true

      How to reproduce the issue

      1. Install AM and amster 6.5.0 
      2. connect -i  as admin
      3. Perform a export:
        amster openam.example.com:18080> export-config --path ./myExportedConfigFiles20181128 --failOnError true
      Expected behaviour
      Amster exports AM configuration
      Current behaviour

      We get the following error - however  some files are exported - approx 222, 51 directories  on a fresh install.

      ERROR java.lang.IllegalArgumentException:
      Illegal character in path at index 11: json/users/{user}/devices/2fa/webauthn?_queryFilter=true
      at org.forgerock.amster.org.forgerock.openam.sdk.http.HttpSessionImpl.createRequest (HttpSessionImpl.java:244)
      at org.forgerock.amster.org.forgerock.openam.sdk.http.HttpSessionImpl.createRequest (HttpSessionImpl.java:251)
      at org.forgerock.amster.org.forgerock.openam.sdk.http.HttpSessionImpl.request (HttpSessionImpl.java:202)
      at org.forgerock.amster.org.forgerock.openam.sdk.crest.CrestResourceProviderAsync.queryCollectionWithFilter (CrestResourceProviderAsync.java:412)
      at org.forgerock.amster.org.forgerock.openam.sdk.crest.HttpCrestResourceProvider.queryCollectionWithFilter (HttpCrestResourceProvider.java:357)
      at org.forgerock.amster.org.forgerock.openam.sdk.operations.CrestOperations.queryWithFilter (CrestOperations.java:490)
      at org.forgerock.amster.org.forgerock.openam.sdk.operations.CrestOperations.queryWithFilter (CrestOperations.java:475)
      at org.forgerock.openam.amster.loadster.exporter.EntityWriter.writeCollection (EntityWriter.groovy:85)
      at org.forgerock.openam.amster.loadster.exporter.GenericExporter.exportEntity (GenericExporter.groovy:29)

      Work around

      On local testing if I set 
      --failOnError false

       or leave the  failOnError flag out of the command the export will just  log and skip webauthn entity export and continue with other export entities.

      It should be possible to use the exported files  import as normal.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                peter.major Peter Major
                Reporter:
                jonthomas Jonathan Thomas
              • Votes:
                2 Vote for this issue
                Watchers:
                19 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: