VCST-4576: Token validation setting, Mixed auth scheme instead of custom scheme provider#3006
Open
ksavosteev wants to merge 17 commits intodevfrom
Open
VCST-4576: Token validation setting, Mixed auth scheme instead of custom scheme provider#3006ksavosteev wants to merge 17 commits intodevfrom
ksavosteev wants to merge 17 commits intodevfrom
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
ksavosteev
changed the title
ksavosteev
changed the title
Contributor
🧪 Katalon Test Report — ✅ PASSED
📋 Suite details
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4562323. Configure here.
|
OlegoO
approved these changes
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
References
QA-test:
Jira-link:
https://virtocommerce.atlassian.net/browse/VCST-4576
Artifact URL:
Note
High Risk
Changes core authentication/authorization defaults and token validation behavior, which can affect API access paths and session revocation semantics across all endpoints.
Overview
Authentication/authorization is refactored to use a new mixed default scheme (
PlatformConstants.Security.AuthenticationSchemes.MixedScheme) implemented via anAddPolicySchemeselector that forwards to Bearer (OpenIddict validation), Basic, API key, or cookie auth, replacing the oldCustomAuthenticationSchemeProviderapproach and updating permission policies to target the mixed scheme.Token/session handling is tightened and made configurable. A new
AuthorizationOptions.EnablePersistentStorageTokenValidationtoggle enables OpenIddict authorization/token entry validation (immediate revocation via DB), and session revocation is expanded:IUserSessionsServicegainsTerminateUserSessions(TerminateUserSessionsRequest)(supports excluding current session group),SecurityControllernow terminates sessions after successful password change/reset, and the user lockout/token revocation event handler switches to usingIUserSessionsServiceinstead of directly revoking viaIOpenIddictTokenManager.UI updates broadcast a password-changed event after reset so the sessions widget refreshes its session count.
Reviewed by Cursor Bugbot for commit 88e00c2. Bugbot is set up for automated code reviews on this repo. Configure here.
Image tag:
ghcr.io/VirtoCommerce/platform:3.1023.0-pr-3006-88e0-vcst-4576-88e00c20