Activities of "Repunjay"

IPermissionManager type also throwing an error as below

IdentityUserAppService Error, below are screen shots.

already provided the Options but still its showing Options are not provided.

Could you please provide example/sample code for the above mentioned IBasicRepository Implementation?

IdentityRoleRepository.ToEfCoreRepository

Hi Thanks for your reply, but some of the ABP Interfaces doesn't contain the definition for GetQueryableAsync() also (attached screen shots), how to do handle this kind of errors?

The System.Text.Encodings.Web package is owned by Microsoft and used by the ABP Framework. See the reference github.com/abpframework/Volo.Abp.Core.csproj.

You can update it in your project to the latest version 5.0.1 Install-Package System.Text.Encodings.Web -Version 5.0.1

As I mentioned earlier, we don't refer to System.Text.Encodings.Web package directly into our project. It seems an indirect dependency into our project through Volo.Abp.Core library. Please suggest -

1. Which version of Volo.Abp.Core package should be used/upgraded in project to mitigate the dependency. Currenlty, we are using version 4.3.1 OR
2. Will directly referrring/updating our project to use System.Text.Encodings.Web package resolve the issue.

Logout

Hi, Thanks for your reply. However, this approach is not feasible for our requirement. What we need is -

• A report with list of users present in the system with last login date and time. The management needs such kind of report on a need basis. Is there a way query this information and provide it for all the users in the system.

• When I try to filter security logs by action as Logout, I don't see any results. Looks like the Logout action is not captured in Audit logs.

Try setting AccessTokenLifetime (or also IdentityTokenLifetime if you need) to 15*60 (token values are in seconds).

If you are using hybrid/authorization code flow and using refresh token; also set AbsoluteRefreshTokenLifetime to 15*60.

We have updated AbsoluteRefreshTokenLifetime, AccessTokenLifetime, IdentityTokenLifetime for 60*5 seconds for testing. But the application logs out forcefully even if the user is active. This is one of the important task we are looking to implement ASAP. We will appreciate your quick response.

I couldn't understand your scenario. If you set AbsoluteRefreshTokenLifetime to 60*5, it will absolutely log you out after 5 mins. Keep this time longer and keep your Access and Identity tokens life time shorter so that, if the access token is compromised, it will be refreshed in short amount of time.

This is not related with ABP, you can check identity server docs for more information

Hi,
Thanks for your suggestion. I understand this is not related to ABP but the Identity server is integrated with ABP and thus reaching out to you for advise. Here is what we did but still not able to fix the problem. Will appreciate if you can do a remote call with us to understand and resolve the issue.

Set AbsoluteRefreshTokenLifetime to 60100 i.e. 100 minutes.
Set AccessTokenLifetime to 605 i.e. 5 minutes.
Set IdentityTokenLifetime to 60*5 i.e. 5 minutes.
User remains active but forcefully gets logout after 5 minutes. There is no call to refresh token api from client application when doing such test. So, does application refreshes token automatically based on above settings or there is something additional we need to do to refresh token?

Hello, This issue is related to SecurityStampValidator, you will have to just add below line in WebModule class in ConfigureServices method. It needs this package Microsoft.AspNetCore.Identity in case gives error for SecurityStampValidatorOptions. This will keep user active for 24 hours/ you can change as per your conveniece.

context.Services.Configure<SecurityStampValidatorOptions>(options => options.ValidationInterval = TimeSpan.FromHours(24));

Unfortunately the suggested code changes didn't worked for us. We added the code into Host module class and the user is still logged out forcefully after 5 minutes. Please note we are using .Net + Angular code template (ABP version 4.3.1). Can we have a short remote call to discuss and resolve this issue?

hi

You can implementation your own AWSSESEmailSender, Just like MailKitSmtpEmailSender .

https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MailKit/Volo/Abp/MailKit/MailKitSmtpEmailSender.cs#L15 https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MailKit/Volo/Abp/MailKit/AbpMailKitModule.cs https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MailKit/Volo/Abp/MailKit/IMailKitSmtpEmailSender.cs https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MailKit/Volo/Abp/MailKit/AbpMailKitOptions.cs

Hi,

Please note we already have a SESEmailSender class in our project which is used to send out email notifications thru AWS SES. We want to understand how to invoke/integrate email send method of this class when password is reset by clicking "Forgot Password" ? In the interest of time, can we have a quick call remotely to understand and resolve this issue?

Try setting AccessTokenLifetime (or also IdentityTokenLifetime if you need) to 15*60 (token values are in seconds).

If you are using hybrid/authorization code flow and using refresh token; also set AbsoluteRefreshTokenLifetime to 15*60.

We have updated AbsoluteRefreshTokenLifetime, AccessTokenLifetime, IdentityTokenLifetime for 60*5 seconds for testing. But the application logs out forcefully even if the user is active. This is one of the important task we are looking to implement ASAP. We will appreciate your quick response.

I couldn't understand your scenario. If you set AbsoluteRefreshTokenLifetime to 60*5, it will absolutely log you out after 5 mins. Keep this time longer and keep your Access and Identity tokens life time shorter so that, if the access token is compromised, it will be refreshed in short amount of time.

This is not related with ABP, you can check identity server docs for more information

Hi, Thanks for your suggestion. I understand this is not related to ABP but the Identity server is integrated with ABP and thus reaching out to you for advise. Here is what we did but still not able to fix the problem. Will appreciate if you can do a remote call with us to understand and resolve the issue.

Set AbsoluteRefreshTokenLifetime to 60100 i.e. 100 minutes. Set AccessTokenLifetime to 605 i.e. 5 minutes. Set IdentityTokenLifetime to 60*5 i.e. 5 minutes. User remains active but forcefully gets logout after 5 minutes. There is no call to refresh token api from client application when doing such test. So, does application refreshes token automatically based on above settings or there is something additional we need to do to refresh token?

Try setting AccessTokenLifetime (or also IdentityTokenLifetime if you need) to 15*60 (token values are in seconds).

If you are using hybrid/authorization code flow and using refresh token; also set AbsoluteRefreshTokenLifetime to 15*60.

We have updated AbsoluteRefreshTokenLifetime, AccessTokenLifetime, IdentityTokenLifetime for 60*5 seconds for testing. But the application logs out forcefully even if the user is active. This is one of the important task we are looking to implement ASAP. We will appreciate your quick response.