[SCA] No permissions displayed when creating an SCA policy.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[SCA] No permissions displayed when creating an SCA policy.

L1 Bithead

Hi,

I've been trying to configure an SCA policy for AWS Identity Center. The page opens an I can see accounts but when I click on an account, no permission sets are found, even though there are multiple for each account. Any idea on how to fix it? The AWS workspace (organization) is connected and working. See below for exampleField_Content_versions_oct20__068Ht00000UJkNMIA1.png

1 accepted solution

Accepted Solutions

L1 Bithead

Hello everyone,

 

Little [update] on this case: I was able to fix the issue and the permission sets are now displayed correctly in the UI. However, I have another issue with the error code P1028 "SCA couldn't add this identity to the policy because there's no custom role associated with the relevant web app." for which a remediation is given "Create a custom role for the relevant web app in the format AWS_SCA_<management account ID>, then add the identity again." after creating a policy. As there isn't a lot of details in the documentation, I wasn't able to fix the issue yet.

 

[How to fix-display issue] My problem was due to the SCA IAM role which was named CyberArkRoleSCA{management account ID} instead of CyberArkRoleForSCA{management account ID}. I guess this caused the CyberArk SCA account not to use the right role. The issue was fixed by creating a new IAM role with the name CyberArkRoleForSCA{management account ID} and the same policies/trust relationships as the one created previously. I guess this comes from an error in CyberArk's automated stack deployment.

View solution in original post

9 REPLIES 9

L3 Networker

Hi @Adrien Chevalier​ ,

 

You can check the following steps:-

  1. Verify Permissions: Ensure the necessary AWS IAM and Identity Center permissions are granted, including sso:CreateAccountAssignment, sso:DescribePermissionSet, and identitystore:ListUsers.
  2. Check Connection: Confirm that the AWS workspace is properly connected and synchronized with CyberArk.
  3. Configuration: Make sure the AWS organization and roles are correctly set up as per the CyberArk SCA documentation.
  4. You can also check this link --> AWS IAM permission update | CyberArk Docs

L3 Networker

Hi @Adrien Chevalier​ ,

 

You can check the following steps:-

  1. Verify Permissions: Ensure the necessary AWS IAM and Identity Center permissions are granted, including sso:CreateAccountAssignment, sso:DescribePermissionSet, and identitystore:ListUsers.
  2. Check Connection: Confirm that the AWS workspace is properly connected and synchronized with CyberArk.
  3. Configuration: Make sure the AWS organization and roles are correctly set up as per the CyberArk SCA documentation.
  4. You can also check this link --> AWS IAM permission update | CyberArk Docs

Hi @Avi Singh Rathore​,

 

Thanks for the answer. I checked every steps and it didn't fix the issue unfortunately...

L3 Networker

hi @Adrien Chevalier​ thank you for your question. I’ve shared it to our SCA Product Resource Center (just launched!) If you haven’t joined the group, I encourage you to do so. Our goal is to build a digital hub for all things SCA (resources, docs, questions, etc.) and we will be monitoring the feed closely for any questions that come through. The team is looking into this now.

Thank you @Kellie Passineau​, I'm joining the group immediately! Wishing a lot of success for this group 🙂

Hi @Adrien Chevalier​ - Our team looked into this & identified the onboarding of CEM as the issue. We can help dig into this further with you via our Support team. Can you please open a case for assistance?

 

To create a support ticket for your organization, please use the "Services Hub" page (found in the top menu as well as on the home page of the Tech Community) and go to the “Create Requests and Review Cases” section to open a case.

 

Note:

If you do not have access to open support cases (i.e., if you cannot see the "Cases" section), please reach out to one of your team members who has access to Support to raise a ticket on your behalf.

L1 Bithead

Hello everyone,

 

Little [update] on this case: I was able to fix the issue and the permission sets are now displayed correctly in the UI. However, I have another issue with the error code P1028 "SCA couldn't add this identity to the policy because there's no custom role associated with the relevant web app." for which a remediation is given "Create a custom role for the relevant web app in the format AWS_SCA_<management account ID>, then add the identity again." after creating a policy. As there isn't a lot of details in the documentation, I wasn't able to fix the issue yet.

 

[How to fix-display issue] My problem was due to the SCA IAM role which was named CyberArkRoleSCA{management account ID} instead of CyberArkRoleForSCA{management account ID}. I guess this caused the CyberArk SCA account not to use the right role. The issue was fixed by creating a new IAM role with the name CyberArkRoleForSCA{management account ID} and the same policies/trust relationships as the one created previously. I guess this comes from an error in CyberArk's automated stack deployment.

Hi @Adrien Chevalier​  - Glad you were able to work through the first issue you were experiencing. In regards to the P1028 error, its referencing an Identity role that needs to be created as part of the "add aws to the user portal" section of the documentation. Please take a look here https://docs.cyberark.com/sca/latest/en/Content/DPAforCloud/sca_define-web-app-in-identity.htm#CreateaAWSwebappinIdentityAdministration , make sure you select AWS IAM Identity Center, and then you'll see the section called "To specify the AWS application settings" which walks through creating this specific role. Please do follow up if you're still having an issue, and a support ticket can also help us reach out directly to get you timely support!

 

Field_Content_versions_oct20__068Ht00000VbpSPIAZ.png

Hi @Mike Bykat​, 

thank you for the explanation, I guess I skipped a few steps but now everything seems to work fine!

  • 1 accepted solution
  • 422 Views
  • 9 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!