<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z000091OrL2CAKOkta Classic EngineAdministrationAnswered2023-04-14T21:57:18.000Z2023-04-11T10:59:10.000Z2023-04-14T21:57:18.000Z

FabioT.22923 (Customer) asked a question.

User attributes scope not "User Personal" doesn't work

We are integrating AWS with Okta SAML/SCIM and trying to use some attributes at the group level:

We assigned a value to the attributes available under Applications->AWS->Assignments->Groups->Edit (on XYZ group) but this value is not propagated through SCIM and is not documented if and how should be used with SAML assertions.


  • Hi @FabioT.22923 (Customer)​ , Thank you for reaching out to the Okta Community!

     

     

    The catalog app for AWS does not support Provisioning, as stated in the template guide: 

    image 

    As for the SAML part of the configuration, that is hardcoded as well and does not offer the option to add additional attribute statements.  

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
    • FabioT.22923 (Customer)

      Actually, we are using the "AWS IAM Identity Center" that should be fully SAML/SCIM compliant

      • Understood.

        I've looked into that one now and the Provisioning part seems to be "partner-built" so I'm no sure if there's much we can do from the Okta side to troubleshoot.

        Feel free to open a case and discuss the matter with one of our Support Engineers, but I also recommend reaching out to the service provider support.

        Expand Post
    • FabioT.22923 (Customer)

      I think you missed my point, we have the integration up and working with SAML and SCIM, the issue is related to group attributes not propagated correctly

      • DonF.81354 (Customer)

        Yes, please see below for how that would be configured:

         

        imageIn the name, please specify the principle tag you are wanting to use, and the value such as "PrincipalTag:<insert value here>"

         

        Then in the group assignment of the AWS SSO app, insert that same value for the attribute like so: image Finally, I recommend you download and install the SAML Tracer plugin to help identify what is being sent over. Thanks!

        Expand Post
This question is closed.
Loading
User attributes scope not "User Personal" doesn't work