- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 03:10 PM
ATF Test keeps failing when creating a user and adding a role.
I am trying to run the OOB GRC Test - GRC: Create Authorization Boundary and Authorization Package. The Test keeps failing when creating User and adding a role. I get the Failure message: FAILURE: Could not add role 'sn_irm_cont_auth.info_system_sec_officer' while creating user with id '8eeb1f538328e21016cb78c6feaad395'.
I have placed a false on the step for Authorized official and went to the next user and that fails as well and so on....All of the roles are in the Roles Table.
This is happening on my project with my work instance and my PDI. any suggestions will help. This is not an Admin role issue. I'm running the test as the System Admin. Your help and direction is much appreciated.
Best,
MP
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2025 12:41 AM - edited 04-05-2025 01:10 AM
Hi @Myrtle_37
This a known bug. To resolve that, in the step 3, you need to uncheck the "Impersonate this user" check box. Once it's done it'll run as expected.
Hope this helps.
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 10:34 PM
Hello @Myrtle_37
Is the scope same ? Are you able to add that role in platform in exactly same scope and same access permissions as you are doing in test step ?
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2025 03:29 AM
I'm in the same scope. The issue is fixed with J. Silva's explanation. Thank you for responding to my Isuue. Much Appreciated.
Best,
MP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2025 12:41 AM - edited 04-05-2025 01:10 AM
Hi @Myrtle_37
This a known bug. To resolve that, in the step 3, you need to uncheck the "Impersonate this user" check box. Once it's done it'll run as expected.
Hope this helps.
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2025 03:25 AM
Hi J. Siva. This worked! Thank you. Is this known issue documented somewhere? Also, In order to Impersonate the System Owner would I need to add a separate test for that? Thank you again!
Best,
Myrtle