[OPENAM-14049] Amster export failure Created: 29/Nov/18 Updated: 27/Dec/20 Resolved: 07/Dec/18
|Fix Version/s:||220.127.116.11, 6.5.1, 7.0.0|
|Reporter:||Jonathan Thomas||Assignee:||Peter Major [X] (Inactive)|
|Labels:||AME, Must-Fix, Newton|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||2018.16 - Tin|
|Support Ticket IDs:|
|Needs QA verification:||
|Are the reproduction steps defined?:||
Yes and I used the same an in the description
Amster export fails with
We get the following error - however some files are exported - approx 222, 51 directories on a fresh install.
On local testing if I set
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.
|Comment by Jonathan Thomas [ 29/Nov/18 ]|
Following suggests that Amster tests pass.
Will need to verify that this is not just an output error.
|Comment by Peter Major [X] (Inactive) [ 07/Dec/18 ]|
Jonathan Thomas The tests were not meant to pass, I've updated the code so that failing export/import commands will break the tests.
|Comment by Filip Kubáň [X] (Inactive) [ 10/Jan/19 ]|
Verified on ForgeRock Access Management 18.104.22.168-RC1 Build d901475564 (2019-January-10 06:24)
Config was exported as expected, exported data can also be imported without any issue.
|Comment by Ľubomír Mlích [ 25/Mar/19 ]|
Reproduced in ForgeRock Access Management 6.5.0 Build f8ac1261d9 (2018-November-28 15:19)
Verified as fixed in ForgeRock Access Management 6.5.1-RC2 Build 6e42f86d08 (2019-March-20 19:43)
|Comment by Peter Major [X] (Inactive) [ 14/May/19 ]|
Webauthn devices are user specific, they are not AM configuration.