<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
0D5WR00001P7KJn0ANOkta Classic EngineIntegrationsAnswered2026-05-14T16:37:43.000Z2026-03-06T11:50:29.000Z2026-05-14T16:37:43.000Z
SAML Okta Application - Push Groups Error : The attribute display is not defined in schema.

We are attempting to integrate Okta and Kiro following this documentation https://kiro.dev/docs/enterprise/identity-provider/okta/. All of the steps work fine and even we are able see the users on the Kiro side after the configurations. However when we attempt to use the Okta Push Groups functionality we get errors.

 

I created a group named Kiro.App.Pro in the Okta Directory and added a user. When I attempted to push this group using the Okta "Push Groups" feature from the Okta applicaiton (Kiro-SAML) it results in the following error :

 

Failed on 03-06-2026 11:41:58AM UTC: Unable to update Group Push mapping target App group App.Kiro.Pro: Error while creating user group App.Kiro.Pro: Bad Request. Errors reported by remote server: display: The attribute display is not defined in schema.

 

Next I created another group named Kiro-App-Pro in the Okta Directory with a single user added to it. Then pushing this group results in the following error :

Failed on 03-06-2026 11:41:58AM UTC: Unable to update Group Push mapping target App group Kiro-App-Pro: Error while creating user group Kiro-App-Pro: Not Implemented

 

Screenshot 2026-03-06 at 11.54.22Would be great if some Okta / SAML / SCIM experts explain what is going wrong here. Is this something due to any issue with the Kiro SAML schema. How can we fix this error and get the Push Groups feature of Okta work seamlessly ?

 

 


  • Hello @NihilsonG.53836 (Customer)​ Thank you for posting on our Community page!

     

    If the Provisioning features are all working as intended just the Push group functionality does not work, this might be a limitation on their side.

    For the first error you can try and see if the Display attribute is being send in the schema, if it is not then you might want to add that in the Profile attribute/Mappings and then retry the group push.

     

    I would recommend to reach out to Kiro support and see what are their limitations on the Provisioning features.

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
  • Hello @NihilsonG.53836 (Customer)​ Thank you for posting on our Community page!

     

    If the Provisioning features are all working as intended just the Push group functionality does not work, this might be a limitation on their side.

    For the first error you can try and see if the Display attribute is being send in the schema, if it is not then you might want to add that in the Profile attribute/Mappings and then retry the group push.

     

    I would recommend to reach out to Kiro support and see what are their limitations on the Provisioning features.

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
  • NihilsonG.53836 (Customer)

    Thank you for your reply. I have reached out to the Kiro team as well and looking for their response.

    In the mean time here is the palyload being sent by Okta to Kiro SCIM server for creating the group as part of the Push Group request. It seems to be the members.display attribute thats causing the trouble. Can we confirm from Okta if its adhering to the SCIM groups schema specifications ?

     

    ====================================================================================================

    [2026-03-07 08:21:46] POST /Groups

    ====================================================================================================

     

    REQUEST HEADERS:

    Accept: application/scim+json

    Accept-Charset: utf-8

    Content-Type: application/scim+json; charset=utf-8

    User-Agent: Okta SCIM Client 1.0.0

    Content-Length: 180

    Host: proxy-scim:5000

    Connection: Keep-Alive

     

    REQUEST BODY:

    {"schemas":["urn:ietf:params:scim:schemas:core:2.0:Group"],"displayName":"App-Kiro-Pro","members":[{"value":"5408e4f8-d0c1-707b-d4e6-d87d97ab7a33","display":"xyz@gmail.com"}]}

     

    REQUEST BODY (Formatted):

    {

    "schemas": [

    "urn:ietf:params:scim:schemas:core:2.0:Group"

    ],

    "displayName": "App-Kiro-Pro",

    "members": [

    {

    "value": "5408e4f8-d0c1-707b-d4e6-d87d97ab7a33",

    "display": "xyz@gmail.com"

    }

    ]

    }

     

    RESPONSE STATUS: 400

    RESPONSE BODY:

    {"schema":["urn:ietf:params:scim:api:messages:2.0:Error"],"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"detail":"display: The attribute display is not defined in schema.","status":"400","exceptionRequestId":"4d271767-5d29-49e7-9948-7436f4fd10cb","timeStamp":"2026-03-07 08:21:46.027"}

    35.81.223.96 - - [07/Mar/2026 08:21:46] "POST /Groups HTTP/1.1" 400 -

    Expand Post
  • Hello @NihilsonG.53836 (Customer)​  Have you checked the Profile Editor for the app and if the display attribute is part of the schema? If it's not, then could you add it and see if that resolves this error?

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post

Loading
SAML Okta Application - Push Groups Error : The attribute display is not defined in schema.