Genesys Cloud - Main

Hello Stijn, 

I have a few ideas on what maybe happening. 

With the GET/api/v2/users/externalid/{authorityName}/{externalKey}:

• I believe the issue you're experiencing with the URL-based authorities is likely because the URL contains special characters that need to be properly encoded. When using this endpoint ensure the authorityName is URL encoded.

With the PATCH operations /api/v2/scim/v2/users/{userId},

- It looks like your approach is close, but needs some tiny adjustments. I have made them below:

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User",
    "urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User"
  ],
  "Operations": [
    {
      "op": "replace",
      "path": "urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds",
      "value": [
        {
          "authority": "https://idp.iamfas.int.belgium.be/fas",
          "value": "abcdefghijk"
        }
      ]
    }
  ]
}

Please note: You need to include both schema URNs, the path should include the full schema reference for externalIds and each SCIM client should use separate Oauth client creds. 

Hope this helps!

Hello,

• I also thought that it was related to the encoding of the url and tried that but didn't succeed.... Thanks for the idea however, but no luck.
  https://api.mypurecloud.de/api/v2/users/userid/externalid/https%3A%2F%2Fidp.iamfas.int.belgium.be%2Ffas --> 
  
  
• The patch operations works indeed. Thanks for the help.

Thanks for your response

{  "schemas": [    "urn:ietf:params:scim:schemas:core:2.0:User",    "urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User"  ],  "Operations": [    {      "op": "replace",      "path": "urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds",      "value": [        {          "authority": "https://idp.iamfas.int.belgium.be/fas",          "value": "abcdefghijk"        }      ]    }  ]}