Activities of "selinkoykiran"

But abp should support both on-premise and cloud deployments, right ? Besides like you said, even without redis customers still change these features via db and this is a problem for also cloud installations. I think we need a solution something like => not persisting these features to anywhere (just runtime). We need to solve this issue it can be a big problem when you sell your product to customers . In someway this feature enabling/disabling thing via redis or db should be prevented ! What can we do at that point, which class should we override FeatureManagementProvider or IFeatureManagementStore ?

Hello, We're using abp's default feature module. For every custom module that we developed, we're creating a class derived from FeatureDefinitionProvider and defining our features . When we run the application, it seems these features are written into our Redis cache and into db . We'll be installing our application with modules (some of them disabled some of them enabled by default) as on-premise. But we realized something. If we go to redis and edit features' values manually then we able to see the hidden modules . Is that a bug for on-premise system or do you have any suggestions about that topic ? Because in that case, even if we close some of the features , customers still can go into redis and change default variables and enable hidden features easily. What should we do in that case, how can we prevent this behavior ? Thank you .

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, )
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

But in that case sometimes we should be able to download , sometimes not , right ? In our case we couldn't download even once. How should we check that if we have one redis ?

Hello , Thank you for that information Yes it is already enabled. What could be the problem then ?

Hello , We have a dockerized served over aws ecs environment. Normally on local there is nothing wrong, it works successfully , but when we try on ecs environment below responses coming from file management download endpoint : the first request which takes the token , seems successfull , (By the way it says succesfull but the response seems empty over google inspect window ):

After that, second request to download with this (unseen over google inspect window) token ends like below:

Like I said we couldn't reproduce the same error on our local , why this token could not be authorized ? Can you help? Thanks.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please first use the search on the homepage. Provide us with the following info:

• ABP Framework version: v7.3.1
• UI Type: Angular / MVC
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello, There aren't any error logs, just some debug and info like I've shared before :

2023-11-01 09:55:04.900 +00:00 [DBG] AuthenticationScheme: OpenIddict.Validation.AspNetCore was not authenticated. 2023-11-01 09:55:04.900 +00:00 [INF] Identity.Application was not authenticated. Failure message: Unprotect ticket failed

Hello , appsetting looks good , I'm sharing below from chrome :

and logs : 2023-11-01 08:48:44.194 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.OpenIddictValidationHandlers+ValidateRequiredTokens. 2023-11-01 08:48:44.194 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was marked as rejected by OpenIddict.Validation.OpenIddictValidationHandlers+ValidateRequiredTokens. 2023-11-01 08:48:44.194 +00:00** [DBG] AuthenticationScheme: OpenIddict.Validation.AspNetCore was not authenticated**. 2023-11-01 08:48:44.195 +00:00 [INF] Request finished HTTP/1.1 GET https://.../index.html - - - 302 - - 5.7613ms 2023-11-01 08:48:54.187 +00:00 [INF] Request starting HTTP/1.1 GET https://.../index.html - - 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessRequestContext was successfully processed by OpenIddict.Validation.AspNetCore.OpenIddictValidationAspNetCoreHandlers+ResolveRequestUri. 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandlers+ResolveRequestUri. 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by OpenIddict.Server.OpenIddictServerHandlers+InferEndpointType. 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by Volo.Abp.Account.Web.Pages.Account.OpenIddictImpersonateInferEndpointType. 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandlers+ValidateTransportSecurityRequirement. 2023-11-01 08:48:54.188 +00:00 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandlers+ValidateHostHeader. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.AspNetCore.OpenIddictValidationAspNetCoreHandlers+ValidateHostHeader. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.OpenIddictValidationHandlers+EvaluateValidatedTokens. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.AspNetCore.OpenIddictValidationAspNetCoreHandlers+ExtractAccessTokenFromAuthorizationHeader. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.AspNetCore.OpenIddictValidationAspNetCoreHandlers+ExtractAccessTokenFromBodyForm. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.AspNetCore.OpenIddictValidationAspNetCoreHandlers+ExtractAccessTokenFromQueryString. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was successfully processed by OpenIddict.Validation.OpenIddictValidationHandlers+ValidateRequiredTokens. 2023-11-01 08:48:54.190 +00:00 [DBG] The event OpenIddict.Validation.OpenIddictValidationEvents+ProcessAuthenticationContext was marked as rejected by OpenIddict.Validation.OpenIddictValidationHandlers+ValidateRequiredTokens. 2023-11-01 08:48:54.190 +00:00 [DBG] AuthenticationScheme: OpenIddict.Validation.AspNetCore was not authenticated. 2023-11-01 08:48:54.191 +00:00 [INF] Request finished HTTP/1.1 GET https://.../index.html - - - 302 - - 3.7031ms

Hello it's all like that, still below exception:

We're having exactly same issues with below link for backend and frontend :

https://support.abp.io/QA/Questions/5722/Publish-Project-in-IIS-server it says it's solved but there isn't any explanation about solution ! Can you share the solution ?

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello,

Like your SignalRTieredDemo.Web we have a MessageEventHandler class in web layer. When we want to send a request from this class to our api host with interface injection (dynamic proxy method) we get the below exception which is Code:Volo.Authorization:010001. And it makes sense actually because this handler starts to work even user doesn't login. It triggered by Rabbitmq.
How can we solve this issue ?

Thank you

• ABP Framework version: v5.3.3
• UI type: MVC
• DB provider: EF Core
• **Tiered (MVC) : yes
• Exception message and stack trace:
• 023-03-10 10:33:24.835 +03:00 [WRN] Exception of type 'Volo.Abp.Authorization.AbpAuthorizationException' was thrown. Volo.Abp.Authorization.AbpAuthorizationException: Exception of type 'Volo.Abp.Authorization.AbpAuthorizationException' was thrown. at Microsoft.AspNetCore.Authorization.AbpAuthorizationServiceExtensions.CheckAsync(IAuthorizationService authorizationService, AuthorizationPolicy policy) at Volo.Abp.Authorization.MethodInvocationAuthorizationService.CheckAsync(MethodInvocationAuthorizationContext context)
• Steps to reproduce the issue:"