There is no problem. It is my duty to check and respond. However, the MVC project should also handle it in the same way.
Actually, it should behave in the same way as you can see in this recording https://drive.google.com/file/d/14XC2Ay4W7Af5qMHDn3xzGV7xgfS82XVw/view
Merhaba, yaşadığınız sorunu kendi tarafımda tekrarlayamadım, ancak hata lokalizasyon tarafından geldiği için başka bir implementasyon ile ilgili olabilir.
Eğer amacınız sadece yetkilendirme ile ilgili değişiklikleri yönetmekse bu dökümana göz atmanızı öneriyorum. Aynı zamanda giriş sayfasını özelleştirmek isterseniz buradaki adımları takip edebilirsiniz.
Hello, actually, I meant that we are checking whether the access token is expired to make the user stay logged in.
If your token is not expired, the user will not be kicked out regardless of checking the ‘remember me’ option. The remember me feature ensures that the user can stay logged in for both cases (access token is expired or not).
Hello, thank you for providing more details. I have created and tried to produce the same problem with this DTO and this endpoint. However, I have not reproduced the same issue. If the problem persists, you can share a sample project within this e-mail address sumeyye.kurtulus@volosoft.com
If your aim is to utilize the Material Dialog component, as far as I have understood, we do not have such a plan in the short term. However, we can discuss this for our long term plans.
Hello, as you may derive from the codebase (https://github.com/abpframework/abp/tree/dev/npm/ng-packs/packages/theme-shared/src/lib/components/modal), ABP modal component supports all the options in the same way with the NgbModalOptions
Since then the open function in the library will handle the options by appending them to the modal refence, you can implement the intended behavior.
If you think that your case is not dependent on this, I can assist you further.
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.
