Redirect to page after login in Angular Guard

I have the following angular-oauth2-oidc configuration (and I am using Identity Server 4):

import { Component } from '@angular/core';

import { AuthConfig, OAuthService, JwksValidationHandler } from 'angular-oauth2-oidc';

export const authConfig: AuthConfig = {
  issuer: 'https://localhost:5005',
  redirectUri: window.location.origin + "/index.html",
  clientId: 'spa',
  responseType: 'code',
  scope: 'openid profile email offline_access api',
  showDebugInformation: true,
  clearHashAfterLogin: false
};

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html'
})

export class AppComponent {
  constructor(private authService: OAuthService) {
    this.authService.configure(authConfig);
    this.authService.tokenValidationHandler = new JwksValidationHandler();
    this.authService.loadDiscoveryDocumentAndTryLogin();
  }
}

And I created the Angular’s 7 Guard:

import { CanActivate, ActivatedRouteSnapshot, RouterStateSnapshot, Router } from '@angular/router';
import { OAuthService, OAuthEvent } from 'angular-oauth2-oidc';
import { Injectable } from '@angular/core';

@Injectable({
  providedIn: 'root'
})

export class AuthenticatedGuard implements CanActivate {

  constructor(private router: Router, private authService: OAuthService) { }

  canActivate(router: ActivatedRouteSnapshot, state: RouterStateSnapshot) {

    if (this.authService.hasValidIdToken() && this.authService.hasValidAccessToken()) 
      return true;

    this.authService.events.subscribe(({ type }: OAuthEvent) => {
      switch (type) {
        case 'token_received':
          return this.router.navigate(['/protected-route']); // How to get the actually route?
      }
    });

    this.authService.initLoginFlow();

    return false;

  }

}

If I try to access a protected route without being authenticated I am redirected to login.

After successful login I am redirected to Angular’s home page but not to the protected route I tried to access …

How to get redirected, after login, to the protected route that I tried to access before?

Shouldn’t I get the route from ReturnUrl parameter?

Should not exist a auth-callback route on Angular’s component to handle this?

I am not sure about the best way to do this.

Thank you

[jeroenheijmans]

You could see if my example implementation for this feature is useful to you?

[jeroenheijmans]

Things went a little quiet here (on my end too). I’m gonna close for now, please track #592 or if you feel this is different post a full (but preferably minimal) repro e.g. on StackBlitz so we can further investigate.