Hi Kamidu,
Please note this issue at [1]. I think the problem is due to this issue.
This has been fixed at [2]. You can apply the patch or get IS 5.1.0. This
is fixed in IS 5.1.0.
Hope it helps.
[1] https://wso2.org/jira/browse/IDENTITY-3009
[2] https://github.com/wso2/carbon-identity/pull/1388
Hi Johann/IS Team,
As per the discussion i had offline earlier above exception occurred under
heavy loads.
The above exception occurred without any high loads in the system.
When one devices logged in for some time, without any concurrent calls to
IS, this exception is given to the device.
Any id
Hi IS Team.
The above error occurs in the 1st token expiration time also,with on device
calling a singleton token refreshing call to IS.
This happens when EMM android agent try to acquire a new set of token on
the access token expiry using the refresh token grant.
This Issue Started after the IS
Hi IS team,
I am getting a "Unique index or primary key violation" exception when
trying to refresh the access token with the refresh token grant type. The
error log is given below.
As per the discussion I had offline with Johann, this seems to be a known
issue which could occur when tested with
