Artwork Processing
PLP upload issues due to auth failures
Incident Resolved: CTIM-1295
Artwork teams have deployed the changes to the Sherbert API and can confirm that it now supports the session-based authentication. This incident is contained. The process of ensuring that all CT services can handle session auth methods will be tracked separately.
Please contact CTIM or see ticket for more details.
UPDATE:
The sherbert team have incorporated the changes in sherbert to support sessions-based authentication and are now testing the flow. Once tested, They should be able to deploy this in production within the next couple of hours.
UPDATE:
The Artwork Sherbert team is currently working on implementing the session tokens. The next update will share after we hear from the Artwork Sherbert team.
UPDATE:
The Artwork Sherbert team is currently investigating and exploring the implementation of the session token. Next update when we hear from them or maximum in 1 hour.
UPDATE:
The Artwork Sherbert team has been notified and we are awaiting their response. The next update will be shared once they begin their investigation. CTIM will follow up on this again within the next 2 hours.
UPDATE:
Vista confirms the initial impact was contained and there’s been no problems since 1pm ET (5pm UTC). Artwork teams are aware of the auth issue with the Sherbert API. We will reach out to them again during their business hours to find out about the next steps needed to allow the session-based auth requests from Vista.
New Incident: CTIM-1295
Priority: High
Escalation sent to: Artwork Tech: Artwork Processing Support for review.
Vista identified an issue earlier today where customers experienced failures on PLP uploads. The original problem was resolved on the Vista side by rolling back a change that had updated the auth library.
This incident is being raised within CT to ensure that the updated session-based auth being used by Vista is supported on CT endpoints. Artwork teams are already aware of the issue but there could be other domains that need to be notified to support this change.
Currently since the impact to customers was resolved earlier, this is raised as a ‘High’ priority incident to be reviewed by the support teams during business hours.