Thank you , ok then in that case we couldn't change the behaviour , because we have one consumer. Maybe we can move this operation into background job (hangfire). What do you think about that approach ?
Hello , We're using RabbitMq as distributed event bus and we're using eto's between different modules for communication. We have a case like => if one of the messages takes to much time to finish then rabbitmq puts that message into unacked side , because consumer didn't return any response (which is normal behaviour). This message is being executed by consumer (our apihost ) (btw the finishing time of that process is not crucial for us). But at the same time we're continuing to send different etos to rabbitmq , too. These 2nd or 3rd messages are kept in also as unacked (which is again normal behaviour). But we don't want to wait this first long-running process , for our small events . The other events shouldn't wait for this first long-running task. Because of that we saw prefetchCount option. When we change prefetchCount to 10 in rabbitmq configurations (default is 1 I guess in abp ) , nothing changed , still our other messages kept as unacked an wait for the first one. Then we read maybe we can create different channels for consumers and producers in same connection. But within abp we couldn't find a way to do that. Why prefetchCount isn't working, can we create different channels ? These approaches make sense to you to solve our issue ? What can be your suggestion on that point ?
Thank you.
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:
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 .
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:
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:
