Activities of "EngincanV"

Hi, the primary way to control the session duration within your ABP application when using an external provider like Azure AD is by configuring the lifetime of the authentication cookie that your application issues. Azure AD controls its own session and token lifetimes, but your application's session is managed separately by the cookie authentication middleware.

So, you can configure your application cookie and set the expiration time to 24 hours like below:

    context.Services.ConfigureApplicationCookie(options =>
    {
        options.ExpireTimeSpan = TimeSpan.FromHours(24); // Set cookie expiration to 24 hours
        options.SlidingExpiration = true;
    });

Regards.

[itlpierre] said:

[enisn] said: Hi,

does it have anything to do with the fact that im using the basic ui template?

I posted an article about that topic, you may want to follow this one for the basic theme:
https://abp.io/community/articles/you-do-it-wrong-customizing-abp-login-page-correctly-bna7wzt5#gsc.tab=0

I'll look into this, will update when I've tried it out

Thanks for the update. We will be waiting for your response.

Hi, the initial loading may take time and unfortunately, this is a limitation of Blazor WASM. If performance is important to you, we suggest using Blazor WebApp, so you can benefit from both Blazor Server and Blazor WASM, and eliminate the initial loading issue.

Also, you may want to check this community article: https://abp.io/community/articles/prerendering-blazor-wasm-application-with-abp-6.x-2v8590g3

Hi, the AuthServer application is an MVC / Razor Pages application, so you can create a _Footer.cshtml under the Themes/LeptonX/Layouts/Application path in your AuthServer project, and then customize the footer. (https://abp.io/docs/latest/ui-themes/lepton-x/mvc#customizing-the-footer-section)

Hi, can you please check if your problem is the same as in this issue (https://github.com/abpframework/abp/issues/10929)?

Hi, the Text Template Management module in ABP Framework supports tenant-specific and culture-specific template customizations out of the box.

However, implementing role-based customization requires more extensive changes. For example, you would need to:

• Extend the AbpTextTemplateContents table to include a RoleId column,
• Modify the application service implementations accordingly,
• Adjust the logic responsible for resolving and rendering templates to factor in user roles.

Since this involves updating several layers (from database to application logic), it’s not straightforward to list all required changes here. We recommend checking the Text Template Management module's source code to identify the key integration points and customize the behavior based on your needs.

Regards.

context.Services.AddIdentity<IdentityUser, IdentityRole>() .AddEntityFrameworkStores<CoreBackendDbContext>() .AddDefaultTokenProviders();

Hi, you don't need to add this configuration, if your project depends on the Volo.Abp.Identity.Pro.Domain project, then there is a similar configuration is already made on the module side. So, you can remove this configuration. Probably, it's causing this problem because it overrides the default registration:

context.Services.AddIdentityCore<IdentityUser>().AddTokenProvider(TokenOptions.DefaultAuthenticatorProvider, typeof(AbpAuthenticatorTokenProvider));

Therefore, can you please remove the related configuration in your side, and check if it fixes the problem or not?

[merdan] said: Ok, thanks for the clarification. Am I right to think that startup templates don't change on patch releases (like in my case, between 9.1.1 and 9.1.3), so I can just update ABP packages and keep other files as is?

Yes, in patch releases we only fix bugs, and typically you don't need to change any file. You can directly switch to stable and continue developing.

Regards.

Hi, while you are checking the Redis Server and fixing the overload problem, do you need anything from our side?

[dhaoo] said: Must the interface defined by *.Application.Contracts be referenced in the module to implement the proxy? Is it referenced in the *.HttpApi project or in the *.httpapi.client

Yes, we suggest defining in a shared library between client and secret, so you can use the application service interface in your client application and generate a proxy for that. (https://abp.io/docs/latest/framework/api-development/static-csharp-clients#service-interface)

Otherwise, you might need to create a httpclient instance yourself, and send a request to the related service endpoint manually. Please refer to https://abp.io/docs/latest/framework/api-development/static-csharp-clients#service-interface for more information.

Regards.