Invalid refresh token after username changed

Getting advice
, ,
1

Steps to reproduce:

  1. Invoke token endpoint
    curl --location --request POST 'http://{{test-endpoint}}/auth/realms/customers/protocol/openid-connect/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'client_id=TestClient' \ --data-urlencode 'client_secret=a5e19616-b807-49a8-9744-fb2daa563127' \ --data-urlencode 'grant_type=password' \ --data-urlencode 'scope=openid offline_access' \ --data-urlencode 'username=test1234@gmail.com' \ --data-urlencode 'password=Test1234'

  2. Change username

  3. Invoke token endpoint for refresh token. Use refresh token from first step’s response.

curl --location --request POST 'http://{{test-endpoint}}/auth/realms/customers/protocol/openid-connect/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'client_id=TestClient' \ --data-urlencode 'client_secret=a5e19616-b807-49a8-9744-fb2daa563127' \ --data-urlencode 'grant_type=refresh_token' \ --data-urlencode 'refresh_token={REFRESH_TOKEN_FROM_FIRST_STEP}'
4. Now is refresh token invalid.
{
“error”: “invalid_grant”,
“error_description”: “Invalid refresh token”
}

Is it correct behaviour, that refresh token is invalid after username changed?

Thanks?