SimpleIdServer

Hello @momostarsky , I believe you're still encountering issues because the lifetime of the request parameter is insufficient. We've increased the lifetime from 120 seconds to 5000 seconds in all...

Hello, This error message should not cause any issues, and the identity provider should continue to function correctly. The exception is thrown when the application runs for the first time....

Hello ! 1. This issue has already been fixed in the release/v6.0.3 branch. 🙂 2. You encountered the exception "Error refreshing access token - Error = invalid client" because the...

3. Offline scope: The offline_access scope can be defined as either an API resource or an identity resource. However, this has no impact on the generation of the refresh token....

Good point! At the moment, in SimpleIdServer, the refresh token can only be used once and cannot be reused. We will add support for multiple uses of the refresh token...

Hello @qq1176914912 , This feature will be added in release 6.0.4. When editing a client's settings, you can now choose the refresh token usage mode: OneTimeOnly or ReUse. According to...

Indeed, there is an issue with the parsing. The issue has been fixed in the branch release/v6.0.4. Kind regards, SID

Hello, Indeed, since version 5.0.3, a new attribute has been added to SCIM. When the property `IsGroupPublishEvtsEnabled` is set to false, the event is not published. Could you please set...

Hello, If the group is empty and does not contain any references to users, only one event — `RepresentationRemovedEvent` — will be published. If the group contains a user, two...

Hello, Some changes have been made to the master branch to ensure that only a single attribute is raised when a reference attribute is added or removed. Each attribute now...