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 ?
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 ?
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, 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:
So what about , permission and feature side , these have different implementation ? Settings domain module doesn't have any saveasync thing , so how does this module persist definition providers at first run ?
Thank you for the IExtraProperties information.
I'm sharing the fluentapi part :
As I shared at first post , even I ignore ProjectId column , it's still creating fk with ProjectId1 ? Thank you .
Hello , Anyone checked this issue ? Just a reminder :)
Thank you.
