So, I\'m trying to protect the access to several routes by using guards. I\'m using the following routes to do so :
const adminRoutes : Routes = [
{
path:
In your example you have called canActivate inside canActivateChild, hence both the guards are getting called when you are traversing among child routes. If you were to have different authentication logic inside both the guards, your canActivate guard won't execute while traversing among child routes.