@maciej-wisniowski
Ok let me explain it to you again, maybe it was not clear enough.
YES the client_id is passed as a parameter to the UserManager of client as well as the post_logout_redirect_url. I do not pass any handmade parameters.
see:
- The oidc-client uses the client_id to get the token, and it works!
- The oidc-client uses the post_logout_redirect_url for logout, BUT the fusionauth ignores it and readirects me to the auth root. The client_id is not sent here by the oidc-client, as by OID default standard.
SO I tried manually to send the so called in the FusionAuth Documentaion "optinal" parameter: client_id for the logout AND taaaadaaaa it works - the FusionAuth redirects to the passed post_logout_redirect_uri Looks that FusionAuth expects beside the post_logout_redirect_uri also the client_id for logout BUT i cannot set the client_id in the oidc-client library for the logout process, because it is not by standard.
Now clear?!