Table of Contents
- Due Date
- Reason for Change
- Integration Changes Required
- What Will Happen Around the Due Date?
This article covers the changes we will be making to the existing "SoapSessionId" cookie value that is returned via our SOAP API. This change will alter the content and value of this cookie.
|Staging||Week of October 28th, 2019|
|Production||To be communicated|
Reason for Change
Earlier this year, NMI started routing requests sent to https://testsoap.cardeasexml.com via load balancers (LB). A part of this change included the addition of a new “SoapRouting” cookie designed to let the LB route requests to the correct WebMIS back-end.
This change caused some integration issues for solutions using Java and the Apache Axis 1.x java2wsdl tool due to poor handling of any cookies other than the Session cookie by the auto-generated code.
To overcome this limitation, the existing “SoapSessionId” cookie is going to be reformatted to allow the routing of requests effectively, whilst removing the “SoapRouting” cookie.
Integration Changes Required
None - this is just a notification change to the cookie value returned by the WebMIS SOAP API.
Please note: Any storage, manipulation, and processing of this cookie should be reviewed as the content and length of this cookie will change.
What Will Happen Around the Due Date?
Around the Due Date, the WebMIS SOAP API will start returning the SoapSessionId session cookie as a base64 encoded string, such as:
instead of the old 24 character alphanumeric session identifier, such as: