You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After looking into it a bit more, it turns out that there are several things that need to be done, and that it may affect some of the SDKs that are generated, because the way it's implemented for some clients is not the way it should work.
There is currently an issue with multiple headers of the same name. For some APIs, there are multiple Set-Cookie headers returned and the way how headers are defined (key-value pairs) doesn't allow to define multiple headers with the same name. There is a workaround which uses null bytes to define multiple Set-Cookie headers.
Preflight checklist
Describe the bug
The rust SDK returns only the flow object and therefore it's not possible to access cookies from the response to forward them.
As example: The JS SDK returns a
AxiosPromise
which contains the complete response. The rust SDK returns only the flow object.Therefore it's not possible to forward the CSRF cookie to the client if I call
create_browser_login_flow
as example.Reproducing the bug
Call the
create_browser_login_flow
of the rust crate.Version
1.0.0
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Docker
The text was updated successfully, but these errors were encountered: