Activities of "shobhit"

Hello maliming, As i am not the expert in ABP features. can you help me out with sample where i have to make changes.

• ABP Framework version: v4.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

1- go to administration --> identity management --> Roles 2- select Permission option for any role 3- Assign all permission (we have more than 400 permissions) under your project to role 4- click save 5- screen stuck and loader keep roatating infinitely

Hello , Thanks a lot for providing detaild steps. in second last step i am getting this error:

        But my other dotnet commands are working fine.

Hello muhammedaltug , Thanks for help. my App.component.ts constructor looks like this. in last line of code

  .subscribe(() => this.authService.navigateToLogin());
  

.navigateToLogin() method not found. What is missing

constructor( private routes: RoutesService, private oAuthService: OAuthService, private authService: AuthService, private replaceableComponentsService: ReplaceableComponentsService ) { this.oAuthService.events .pipe(filter(event => event.type === 'token_refresh_error')) .subscribe(() => this.authService.navigateToLogin()); }

Hello,

We fixed navigating to the login page when the token expires in version 4.4 with this pr. Can you update your project to version 4.4 and try your steps again ?

Hi, We are using 4.2.2. Can i get fix for this. Currently we cannot upgrade due to release plan.

I am guessing you are not using refresh tokens.

Share your oAuthConfiguration in the envorinment.ts file, please.

oAuthConfig: { issuer: 'https://localhost:44388', redirectUri: baseUrl, clientId: 'MyApp_App', responseType: 'code', scope: 'offline_access MyApp', },

Hello Maliming, Thanks. Can you also guide me where i have to make these changes i.e. project and file.

great. thanks.

• ABP Framework version: v4.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

1. Current process
   1. go to app
   2. navigate to identity page
   3. select tenant
   4. enter username/ email
   5. enter password
   6. login done
2. New expected process
   1. go to app
   2. navigate to identity page
   3. enter username/email
   4. if username/email matches then populate all tenant. user can select the desired tenant from the list.
   5. if username/email don't match then user can search the tenant. (current way)
   6. enter password
   7. login done

Is it feasible to get done option 2. If yes, then how we can achieve this.

Option 1 batter. Can it prevent user to never see the user details page? i.e. if user type identity.aztute.com then after successful login user redirected to app.aztute.com.

else Both options are good to me