It works using the old "@angular/router-deprecated" module, but it doesn't work when using the new "@angular/router". Basically, with the new router module, after the user successfully authenticates the angular2-adal appears to interpret the returned token from Azure AD as a route which obviously errors out with a no match route error. Is there a way to make this work with the new route module? If not, is there a work around for this? I don't want to create my app using the old route library which doesn't look like it'll stay around much longer.
It works using the old "@angular/router-deprecated" module, but it doesn't work when using the new "@angular/router". Basically, with the new router module, after the user successfully authenticates the angular2-adal appears to interpret the returned token from Azure AD as a route which obviously errors out with a no match route error. Is there a way to make this work with the new route module? If not, is there a work around for this? I don't want to create my app using the old route library which doesn't look like it'll stay around much longer.