-
Notifications
You must be signed in to change notification settings - Fork 919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api: add override mechanism for SOAP Header.Cookie #3636
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Left one comment.
be1221b
to
3cfeaaa
Compare
Sessions are consumed by API endpoints via one of: - HTTP Cookie (vim25 for example) - HTTP Header (vmodl2 /rest and /api) - SOAP Header (pbm, vslm, sms for example) The soap.Client had always set the SOAP Header cookie regardless if consumed by an API endpoint. Clients must now opt-in to this behavior if they need it, such as pbm and vslm. This also allows clients to change the name of soap.Header.Cookie (default is still "vcSessionCookie") vcsim: add override mechanism for session mapping On the simulator side, API endpoints can specify where a session is sourced from. Default is still the "vmware_soap_session" HTTP Cookie. The pbm simulator now specifies the "vcSessionCookie" SOAP Header, behaving as real pbm/VC does. Signed-off-by: Doug MacEachern <dougm@broadcom.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Doug!
In 1918984 / PR vmware#3636 we deferred the http.CookieJar lookup until request time. Fallback to using Path="/" if initial lookup fails. Signed-off-by: Doug MacEachern <dougm@broadcom.com>
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sessions are consumed by API endpoints via one of:
The soap.Client had always set the SOAP Header cookie regardless if consumed by an API endpoint.
Clients must now opt-in to this behavior if they need it, such as pbm and vslm.
This also allows clients to change the name of soap.Header.Cookie (default is still "vcSessionCookie")
vcsim: add override mechanism for session mapping
On the simulator side, API endpoints can specify where a session is sourced from. Default is still the "vmware_soap_session" HTTP Cookie. The pbm simulator now specifies the "vcSessionCookie" SOAP Header, behaving as real pbm/VC does.