How to set\pass #id_token received from custom B2C policy and setup MSAL angular from it?

I’m submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[X] Other... Please describe:

This is more of a question: I already get and #id_token from my custom B2C Sign Up policy. However this policy is called from a link in an e-mail, not from the Angular SPA app.

With this in mind, the Angular JS app doesn’t have a callback to process this #id_token.

Is there any way to set the #id_token in the msalService in Angular JS so that the user is logged in automatically?

This id_token from the sign up policy already has all the user info I need to log them in into the application. I wouldn’t like to redirect them to the login page. This is an unnecessary step.

I’d like for something like this function:

UserAgentApplication.prototype.processCallBack = function (hash) {

or

UserAgentApplication.prototype.handleAuthenticationResponse = function (hash) {

[sameerag]

@maheshkumagali Our angular wrapper is currently in progress of being upgraded to be compatible with our msal-core library. @jasonnutter is working on this and will be able to provide the details.

@jasonnutter This could be a use case we should address with our angular work.

[maheshkumagali]

@sameerag

Can you please help on how to achieve the same for msal-angular. We need to have roles in the jwt token that is attached, when we make api calls mentioned in protectedResourceMap. The sample works well when using msal library for js