In our ongoing effort to align with best practices and improve our service offerings, we are updating the header names used for authentication tokens. We are transitioning from X-Auth-Token to Shift-Auth-Token. This update is pivotal for aligning with modern internet standards and ensuring our services remain robust and user-friendly.

Why Change the Header Name?​

The decision to move away from the X-Auth-Token follows guidelines from RFC-6648, which advises against using the X- prefix for application-specific headers. This change is purely nominal and does not affect the underlying security or structure of the tokens themselves. Rather, it's about adopting a cleaner, standardized approach that reduces the risk of conflicts and enhances compatibility with future technological developments.

Key Changes and Dates​

• New Header Name: Starting now, we encourage all users to adopt Shift-Auth-Token in their API requests.
• Deprecation Schedule: The X-Auth-Token will continue to function until the end of July 2024. After this period, only Shift-Auth-Token will be accepted.
• No Change in Token Mechanics: It's important to note that this change is in name only. The security, generation, and handling of the tokens remain the same.

What This Means for You​

For users, the transition will require minimal adjustments. The key change involves updating API calls to use the new Shift-Auth-Token header instead of X-Auth-Token. We recommend making this update at your earliest convenience to avoid any disruptions when the old header is fully retired.

Ensuring a Smooth Transition​

We are committed to making this transition as seamless as possible:

• Updated Documentation: Our documentation has been revised to guide you through using the new Shift-Auth-Token.
• Technical Support: Should you have any questions or require assistance, our support teams are on standby at service.desk@shift.online.
• Reminder Communications: We will send reminders as the cutoff date approaches, ensuring you have ample time to make the necessary changes.

Conclusion​

This update is part of our commitment to maintaining a secure and efficient service environment. By moving to Shift-Auth-Token, we align with current standards and prepare for future advancements without impacting the robust security of our systems.

We appreciate your cooperation as we make this necessary update, ensuring our technology continues to meet the highest standards of reliability and performance.

Version 2.0.0 is Here!​

The Shift Team is excited to announce the release of version 2.0.0 of our Auto Print utility application, featuring several significant enhancements designed to improve efficiency and user experience.

FTP Uploading​

Concurrent Upload Handling​

We've upgraded our file-watcher technology to handle multiple files more efficiently when added simultaneously or within a short period. This enhancement ensures faster processing times and reduced bottlenecks, providing a smoother operational flow.

Direct to Printer Labels​

Printing Order​

We have optimized the default order in which labels are printed, ensuring they are now sorted more predictably as they come off the printer. This update enhances the organization and readability of printed materials, facilitating better workflow management.

Cross-Platform Compatibility​

File Path Handling​

Our application now boasts OS-independent file path handling, setting the stage for our new (experimental) MacOS and Linux builds. This development means users across different operating systems can experience consistent performance and usability.

MacOS / Linux Builds​

For those interested in early access to our MacOS and Linux versions, please contact the Integration team via the service desk. We are eager to extend the capabilities of our utility application to these platforms and welcome your feedback to refine these builds further.

Get Started with Version 2.0.0​

Embrace the new features and improvements by upgrading to version 2.0.0 today.

We thank you for your continued support and are here to assist with any questions or feedback you may have about the new version.