...

The connectors do not send or synchronize password information. If you have web sudo enabled in your Atlassian product and you administrator users defined in the cloud your administrators will experience a traditional login screen when they access admin pages. These logins will also fail as the Atlassian product is not able to verify the password. There are two solutions to this issue: 1) Disable "web sudo" in your setup. 2) Create administrator users in the internal directory.

Why did SCIM sync PATCH requests stop working on Jira 10?

Atlassian has made several changes related to Platform 7. One of the changes is that they now restrict HTTP methods they haven’t implemented, consequently breaking the PATCH request that Kantega SSO accepts as part of the SCIM specification. We have contacted Atlassian in order to solve this problem, and they have created a high priority ticket: https://jira.atlassian.com/browse/JSWSERVER-26162. Meanwhile, the existing workaround is to use the API Server. Using this endpoint you can use your frontend server/reverse proxy to terminate the HTTPS and map to HTTP on the bind port.

So the request directly to the API server will be:

curl --location --request PATCH 'http://YOUR_JIRA_HOST:5501/scim/YOUR_SCIM_TENANT_ID/v2/Users/2612370c-dd6b-464d-b4cc-b33b648fed93' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_TOKEN_HERE' \
--data-raw '{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:PatchOp"
    ],
    "Operations": [
        {
            "op": "replace",
            "path": "userName",
            "value": "ryan3"
        }
    ]
}'

Kerberos

Keytab files

How do I create a keytab file?

...