Association JIT provisioned users' functions fails

[Thumimku]

Describe the issue:
We got a regression this year, when analysing the impact of the regression with other functionalities following issues were found.

Issue 1- MyAccount Personal Info is broken

How to reproduce:

• Configure a JIT provisioning scenario with association. Please make sure to add the following configuration to the deployment.toml file.

[authentication.jit_provisioning]
associating_to_existing_user = "true"

• Login for the first time (the association will be created with the local user).
• Access MyAccount with the local user

Expected behavior:
MyAccount Personal Info should work

Issue 2- Obtained JWT token has invalid subect id

How to reproduce:

• Configure a JIT provisioning scenario with association. Please make sure to add the following configuration to the deployment.toml file.

[authentication.jit_provisioning]
associating_to_existing_user = "true"

• Change the Access token type in OIDC protocol to JWT
• Request for scopes like openid internal_login profile
• Login for the first time (the association will be created with the local user).
• Get the JWT token and check the sub claim
• Try to call SCIM me call it fails with following msg.

{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "detail": "User 748ca69d-57b9-45c2-80e4-6fe3bad80674 does not exist in: PRIMARY",
    "status": "404"
}

Expected behavior:
SCIM call should work.

Environment information (Please complete the following information; remove any unnecessary fields) :

• Product Version: IS 7.10-m2
• OS:Ma
• Database: H2
• Userstore: Primary