Base solution for your next web application

Activities of "NPECAdmin"

Our objective is to implement an automatic site logout feature after a session timeout of 14,400 seconds (4 hours) on our platform for both normally logged in and for impersonated users. To achieve this, we have configured the Session Timeout Control in the ABP framework under Settings -> User Management. Specifically, we enabled the Session Timeout Control and set the timeout duration to 14,400 seconds.

The current behaviour allows the site to log out users only if they are inactive for the entire 14,400 seconds. However, we require the site to log out users even if they are active. To address this, we attempted to modify the response of the Authenticate API in the TokenAuthController as follows:

int expireTokenInSeconds = await SettingManager.GetSettingValueAsync<int>(AppSettings.UserManagement.SessionTimeOut.TimeOutSecond);

return new AuthenticateResultModel
{
    AccessToken = accessToken,
    ExpireInSeconds = expireTokenInSeconds,
    RefreshToken = refreshToken.token,
    RefreshTokenExpireInSeconds = expireTokenInSeconds,
    EncryptedAccessToken = GetEncryptedAccessToken(accessToken),
    TwoFactorRememberClientToken = twoFactorRememberClientToken,
    UserId = loginResult.User.Id,
    ReturnUrl = returnUrl
};

While this modification successfully redirects the site to the logout screen after 14,400 seconds, triggered by any API call, it displays a "Current user not logged in" error message. Our objective, however, is to have the site automatically log out after 14,400 seconds without requiring an API call and handle this in the UI itself.

We seek your guidance and assistance in resolving this matter. Please provide instructions or insights on how to achieve automatic site logout after the specified duration, directly handled within the UI, without the need for additional API calls.

We are using ABP v12.2.0 with angular.

Thank you for your support.

Hi @ismcagdas

Created a new issue in the above specified repository. https://github.com/aspnetzero/aspnet-zero-core/issues/4974

Thanks.

Reproduction steps: Login either as Host/Tenant Open Users page Click on Create/Add New User button Click on Change profile picture -> Upload a Picture in opened pop up Provide required details like First Name, Last Name, Email Address, Username, etc and click on Save. Click refresh button -> open the newly created user record and verify if uploaded image is displaying for new user or not. Close all pop ups and click on square shaped button on right top, displaying after username and you can find uploaded image is assigned to existing User but not to newly created user. Note: We are using Asp Net Zero v12.2.0

When the profile picture is uploaded at the time of user creation, uploaded picture is updated to current logged in user instead of created on the the new user. I would expect it to not change the current user logged in and instead be created on the new user

when we try create a Mass notification and add more than 5 users to it, CreatorUserId is inserting as null in table [AbpTenantNotifications]. Due to this, notifications with >5 users are not displaying in Mass notifications page. Why is the CreatorUserId not set?

Product Version: 11.0 Product Type: Angular Framework: .net core ABP Framework: v7

Question from our developer: "we need to update display name and description for permission defined in AppAuthorizationProvider SetPermissions in runtime by the end user"

this was reolved it was internal issue!

10.3

When we upgraded to 10.5 hello, the angular code just has errors in two files 'dynamic-entity-property.component.html' and 'dynamic-entity-property.component.ts', when i search for this error i found in asp.net zero support fixing for this but when we try it is not resolved. Can you please help? All the errors are in the screenshots (6 in total)

the link is not exist give me a 404

Showing 1 to 10 of 13 entries