Describe the problem you'd like to have solved
My identity provider is complaining that the query params I call Authorize with contains the httpInterceptor.
In fact, after looking at the networking tab, it seems I really redirect with httpInterceptor in the params.
[...]&httpInterceptor=%5Bobject%20Object%5D&ui_locales=fr&response_type=code&response_mode=query
If I remove the httpInterceptor from the AuthConfig, it is then not sent in the URL.
Describe the ideal solution
httpInterceptor shouldn't be included in the queryParams call to Authorize.
Alternatives and current work-arounds
Not use the official HttpInterceptor.
Additional context
Since right now, I use multiple Auth Providers, I'm cornered because on one side, there's #86 that force me to use the default interceptor and on the other, there's this queryParams that breaks my Auth0 if I don't use a custom interceptor.
Describe the problem you'd like to have solved
My identity provider is complaining that the query params I call Authorize with contains the httpInterceptor.
In fact, after looking at the networking tab, it seems I really redirect with httpInterceptor in the params.
[...]&httpInterceptor=%5Bobject%20Object%5D&ui_locales=fr&response_type=code&response_mode=query
If I remove the httpInterceptor from the AuthConfig, it is then not sent in the URL.
Describe the ideal solution
httpInterceptor shouldn't be included in the queryParams call to Authorize.
Alternatives and current work-arounds
Not use the official HttpInterceptor.
Additional context
Since right now, I use multiple Auth Providers, I'm cornered because on one side, there's #86 that force me to use the default interceptor and on the other, there's this queryParams that breaks my Auth0 if I don't use a custom interceptor.