Activities of "sumeyye.kurtulus"

Hello, I have investigated this case with the related fix that you have mentioned. As the explanation implies here, the expected behavior is to check the related tokens together with the remember me option. So, the logic is not independent from them.

 private checkRememberMeOption() {
    const accessToken = this.oAuthService.getAccessToken();
    const isTokenExpire = isTokenExpired(this.oAuthService.getAccessTokenExpiration());
    let rememberMe = this.rememberMeService.get();

    if (accessToken && !rememberMe) {
      const rememberMeValue = this.rememberMeService.getFromToken(accessToken);

      this.rememberMeService.set(!!rememberMeValue);
    }

    rememberMe = this.rememberMeService.get();
    if (accessToken && isTokenExpire && !rememberMe) {
      this.rememberMeService.remove();
      this.oAuthService.logOut();
    }
  }

Hello, this specific proxy generation problem could have been solved within this release by this fix.

If you think that your case is different, you can provide more detail so that I can assist you further.

Hello, I can suggest you to utilize the component replacement feature that framework proposes to override the default login page. In this case, you will need to consider AuthWrapperComponent to replace with a custom one.

After the replacement, you can also implement your custom logic for the account/admin route in the same way.

Hello, I have carefully investigated your case and realized that this issue was addressed before. If you just remove the :: separation, the problem should be solved. Here is the related issue and documentation references.

Thank you for your cooperation.

Thank you for providing extra details. Currently, we do not have an option to customize this text. You can follow the next releases to be able to customize it.

May I ask for your license type?

Hello, I recommend you to follow this documentation part to customize the AuthWrapperComponent. The auth wrapper component comes from @volo/abp.ng.account/public , so you can import it like this:

import { eAccountComponents } from '@volo/abp.ng.account/public';

Hello, since then we have published the previous patch recently, we will be releasing the next one in the upcoming week.

I am pleased to hear that. Additionally, I will be addressing the other import issue as well. So, you can follow this issue within the releases 🙏If you prefer a workaround, you can replace the wrong imports with this @volo/abp.ng.text-template-management/proxy

I could not duplicate the same problem unfortunately