Set User Authentication Token Validity
SeaVantage provided two ways for users to authenticate: Basic Auth by providing a username and password and
and authentication using a user authentication token generated within the system.
•
In the case of user authentication tokens, their use as an authentication method for SVMP embedding in web pages can lead to unfiltered exposure of the token in web URLs, which can cause security issues if the token is compromised.
•
Therefore, to minimize security issues, we're going to set a validity period (up to 24 hours) for user authentication tokens.
•
If you have fixed user authentication tokens as part of your internal integration with SVMP (API, Web Embed), you will need to modify them.
Changing How Shipment Tracking Results Are Delivered
Traditionally, when customers requested tracking for their shipments, we would notify them of the results immediately upon request.
With this change, when a customer requests cargo tracking (post /v2/cargo), SVMP first stores the request and responds with the results of the storage. You can retrieve the results of the cargo tracking as before via the Get cargo tracking information API (get /v2/cargo/search).
Due to the above changes, the below follows.
•
Two additional status values are added to the bl_status item that was previously present in the shipment tracking results.
◦
Processing (Tracking shipment in progress after tracking request):
◦
Fail (tracking failed)
◦
Before (POL Pre-departure)
◦
On (POL Departure ~ Before entering the POD)
◦
End (POD Port of Entry)
◦
Pending (Booking Confirmation after Full Carry-On Transfer / Destination Carrier (HMM, Maersk)
•
Therefore, for a cargo tracking request (post /v2/cargo), you only need to make a single request when the M-B/L is first registered in FMS. Duplicate requests will result in a 409 Conflict response.
•
If the status value of the shipment tracking result is Fail, please check it separately.
Therefore, we'll keep you posted on the details of the above changes.