Angular-auth-oidc-client: UserData support for azure b2c

Created on 14 Dec 2017  路  8Comments  路  Source: damienbod/angular-auth-oidc-client

Hi, we decided to choice your library because it has best feature of all oidc b2c libraries but one feature it is still missing for azure b2c.
Generaly I got a problem with token renew and after analyse the code I understood that problem is cause userData has empty string. UserData is based on userInfo endpoint that azure dont provide yet. Currently for my own purpose to get all user claims I am using .oidcSecurityService.getPayloadFromIdToken(). The problem is userData inside the library is empty and token renew is not working.
Can you support the path when well_known_configuration don't contain userInfo endpoint then userData should be taken from oidcSecurityService.getPayloadFromIdToken().

It would be nice if we would got that feature in future release.

bug

All 8 comments

@paszkowskik thanks

If you set the auto_userinfo to false, the user data is not used. This should work, otherwise this is a bug which I will fix pending your feedback.

Hope this helps greetings Damien

Thank you for very fast replay. Unfortunetly we have auto_userinfo = false and this case that i wrote before is happens no matter of that flag.

@paszkowskik I will support this then as soon as possible. Want to do a fix this weekend, will add this fix, if I find the bug

thanks for reporting

openIDImplicitFlowConfiguration.auto_userinfo = false;

When this is set, the user data is now set from the id_token.

Will merge and release, once I get a test fixed.

Thank you very much. We are waiting for release.

fixed in 3.0.9, Could you pleace validate this, would be grateful for feedback

We will check it tommorow when we will come back to work. Good job, we are very thankful.

We can proudly say that problem is resolved. First case userData is working correctly with b2c when flag auto_userinfo = false. Second thing is renew token is working now and that was very important case for us. Only one thing I notice that is a mistake in documentation because to renew token before it expire you must put positive value, not negative like documentation suggest.
Thank you very much.

silent_renew_offset_in_seconds

Makes it possible to add an offset to the silent renew check in seconds. By entering a negivative value, you can renew the tokens, before the tokens expire.

Was this page helpful?
0 / 5 - 0 ratings