On the other hand, ABP doesn't make a license check when you publish your project in Release mode. Please make sure it's on release mode.
hi,
this problem is fixed in the newer versions. you can upgrade your project to ABP v4.4.3
This is not supported out of the box as the Identity Server changes need to be done. Gettting token is an Identity Server feature, to prevent sending tokens only with username & password, you can customize the Identity Server 4 or you can ask directly to Identity Server contributors https://github.com/IdentityServer/IdentityServer4. Check out https://docs.identityserver.io/en/latest/topics/custom_token_request_validation.html
Sorry but this is a 3rd party question and we have limited support on 3rd party library questions.
can you pls write your specific question? thanks
ok thank you. we can keep this open.
I mean ABP Commercial has beta version as well. What's the ABP version? (it's written in your csproj files)
see an example https://github.com/abpframework/abp/blob/48c52625f4c4df007f04d5ac6368b07411aa7521/modules/cms-kit/src/Volo.CmsKit.Domain/Volo/CmsKit/Users/CmsUser.cs#L33
this has been addressed and fixed in v5.0. v5.0.0-beta.1 is now online but you can wait for the v5-rc version to update your project. until your update, you can manually fix the case
I know that it's not directly referenced to your project. but if you directly reference it, the vulnerable version will be updated to the latest. do not update a single ABP library! if you want to update ABP, use ABP CLI or ABP Suite to update it all.
directly referencing will overwrite the current version System.Text.Encodings.Web package