You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an end-user has multiple instances of CxSAST that they would like to migrate to a single AST tenant, there is a chance for Group collisions if there are same name Teams on the source CxSAST systems.
Proposed solution
As an added command-line parameter (optional), allow the end-user to specify a prefix for exported values that may collide during Import (to the AST tenant). This initially includes Team Names (that get imported as Groups in AST), but also for any other possible colliding objects.
Additional details
None
The text was updated successfully, but these errors were encountered:
In cxOne, Group Path is the unique field. The name is not.
So /Root/Group1 and /Root/Group2/Group1 are valid groups.
Does it solve your issue?
Do the multiple instances share the same root team name?
Describe the problem
If an end-user has multiple instances of CxSAST that they would like to migrate to a single AST tenant, there is a chance for Group collisions if there are same name Teams on the source CxSAST systems.
Proposed solution
As an added command-line parameter (optional), allow the end-user to specify a prefix for exported values that may collide during Import (to the AST tenant). This initially includes Team Names (that get imported as Groups in AST), but also for any other possible colliding objects.
Additional details
None
The text was updated successfully, but these errors were encountered: