-
Type:
Bug
-
Status: Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 6.0.0
-
Fix Version/s: 6.0.0
-
Environment:ForgeRock Access Management 6.0.0-SNAPSHOT Build 37a804b8c1 (2018-March-22 14:58)
-
Needs backport:No
-
Needs QA verification:No
-
Functional tests:No
-
Are the reproduction steps defined?:Yes and I used the same an in the description
Bug description
Page nodes fail to import
How to reproduce the issue
- Create a tree with a page node e.g.:
- Export all the configuration using amster
export-config --realmEntities 'AuthTree UsernameCollector PasswordCollector DataStoreDecision PageNode' --path /Users/aczv/work/amster/tmp/page.1 --failOnError
- Import that export using amster
import-config --path /Users/aczv/work/amster/tmp/page.1 --failOnError
Expected behaviour
Import succeeds
Current behaviour
Problem 1
[main] ERROR org.forgerock.amster.org.forgerock.openam.sdk.http.DefaultErrorHandler - Unhandled client error: [Status: 400 Bad Request] Failed to import /Users/aczv/work/amster/tmp/22.all.1/realms/root/PageNode/ee0b3bed-edb5-433c-a736-f846934b24f5.json ERROR org.forgerock.amster.org.forgerock.openam.sdk.http.ClientErrorException: 400 Bad Request: Invalid attribute value syntax: '{_id=c20fa235-c750-4013-957c-e8935823b13a, nodeType=UsernameCollectorNode, displayName=Username Collector}'
Problem 2
Despite using the --failOnError flag on the import the tree becomes corrupted
- relates to
-
OPENAM-12700 Amster --failOnError is ignored on import
-
- Closed
-