Open Closed

Exception after ABP update from 9.0.5 to 9.1.1 on password reset flow #9194


User avatar
0
stefan@climatecamp.io created
  • Exception message and full stack trace: ERROR TypeError: Cannot read properties of undefined (reading 'isInternalAuth') at get isInternalAuth (abp-ng.oauth.mjs:489:26)

  • Steps to reproduce the issue: Previously working password reset flow is not working anymore after updating abp to 9.1.1 from 9.0.5. The error seems to be in the account module when it's trying to check "if (authService.isInternalAuth)" and throwing an undefined error.

image.png

image.png


4 Answer(s)
  • User Avatar
    0
    enisn created
    Support Team .NET Developer

    Hi,

    Sorry to hear that.
    Updating client-proxies might be required. Can you check if your client-proxies are updated?
    https://abp.io/docs/latest/framework/ui/angular/service-proxies

    Our @angularteam will help you better in this issue soon.

  • User Avatar
    0
    stefan@climatecamp.io created

    Hello, thanks for the reply.
    Proxies and packages are updated.
    For more context, this undefined error only happens after the user tries to set the password following the email link. The error page which opens seems to be a default one as well and after clicking on the "Home" button the same if check doesn't error out anymore unless trying to set the password again from the email.

    image.png

  • User Avatar
    0
    stefan@climatecamp.io created

    An update on this since the last message is that we managed to have this temporarily fixed by changing the "&__tenant=" query parameter to "&tenant=" and adapting our frontend code to use this.
    Also worth mentioning that we have slightly modified flow than the abp one since our url is pointing to the frontend instead of backend so we're not sure if it's something we missed in the configuration or not.
    But then again, we've had this flow for a long time and it worked fine, only after updating it stopped working.
    Thanks.

  • User Avatar
    0
    sumeyye.kurtulus created
    Support Team Angular Expert

    Hello, sorry for the delayed response. If you are still experiencing the issue, I recommend overriding the authentication guard as a temporary solution until we release an official fix:

    // new-auth-flow-guard.ts
    import { AuthService } from '@abp/ng.core';
    import { inject } from '@angular/core';
    
    export const newAuthenticationFlowGuard = () => {
      const authService = inject(AuthService);
    
      if (authService?.isInternalAuth) {
        return true;
      }
    
      authService.navigateToLogin();
      return false;
    };
    
    

    Then, update your app-routing.module.ts as follows:

    import { newAuthenticationFlowGuard } from './new-auth-flow-guard';
    
    {
      path: 'account',
      loadChildren: () =>
        import('@volo/abp.ng.account/public').then(m => m.AccountPublicModule.forLazy()),
      canActivate: [newAuthenticationFlowGuard],
    }
    
    
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v9.3.0-preview. Updated on May 21, 2025, 13:37