-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 14.0.0
-
Component/s: Amster
-
Sprint:AM Sustaining Sprint 70, AM Sustaining Sprint 71
-
Story Points:3
-
Epic Link:
-
Needs backport:No
-
Support Ticket IDs:
-
Needs QA verification:No
-
Functional tests:Yes
-
Are the reproduction steps defined?:Yes and I used the same an in the description, Yes but I used my own steps. (If so, please add them in a new comment)
When a OpenAM have a site and doing and export-config and import-config and import error happens. Ideally the export/import should work w/o issues.
Import error:
--------------------------------------------------------------------- IMPORT ERRORS --------------------------------------------------------------------- Failed to import /new-export-config/global/Sites/lb.json : 400 Bad Request: Only url, secondaryURLs and _id are valid in write
The issue is that the lb.json have a file "id" in the export that is not recognised by the import
{ "metadata" : { "realm" : null, "amsterVersion" : "14.0.0", "entityType" : "Sites", "entityId" : "lb", "pathParams" : { } }, "data" : { "_id" : "lb", "id" : "02", "url" : "https://openam.example.com:8443/openam", "secondaryURLs" : [ ] } }
- is duplicated by
-
OPENAM-12146 Amster fails to import site config
-
- Closed
-