Bartender Identity Provider Migration
BarTender Cloud will move its identity provider starting October 6, 2024
As part of its next release, BarTender Cloud will change its identity provider to streamline authentication and enhance security of your labeling operations. The move will start rolling out on October 6, 2024.
This process has been designed to be simple and straightforward. BarTender Cloud users will only need to complete two items:
- Re-register your account using new account sign-in URL
- Migrate all access tokens connected to any of the BarTender Cloud APIs.
Please review the information, technical documentation, and resources below to learn how to best prepare.
Actions needed to migrate
For BarTender Cloud Administrators
- Americas Region Only: Add the new outbound IP addresses for all integrations with BarTender – see FAQs for list of IP addresses
- Clear your browser cache
- Reinstall Print Gateway
- Open the automated email from BarTender Cloud – the subject line will be: “Action Required: Updated BarTender Authentication System Notification”
- Click on the Create Password button to reset your password (or use the link provided under the button that is formatted as https://OrgName.account.am1.bartendercloud.com )
- Bookmark the new account sign-in URL
For BarTender Cloud Automation users
- Americas Region Only: Add the new outbound IP addresses for all integrations with BarTender – see FAQs for list of IP addresses
- Clear your browser cache
- Reinstall Print Gateway
- Open the automated email from BarTender Cloud – the subject line will be: “Action Required: Updated BarTender Authentication System Notification”
- Click on the Create Password button to reset your password (or use the link provided under the button that is formatted as https://OrgName.account.am1.bartendercloud.com)
- Bookmark the new account sign-in URL
- Migrate any additional access tokens (e.g., web applications)
Identity Provider Migration Checklist
Below is everything you will need for a seamless transition.
- BarTender Cloud Organization Domain ID
- Updated login credentials
- List of affected client applications (web, consoler, server, etc.)
- List of team members who use BarTender Cloud
Identity Provider Migration Technical Documents
- Getting Started with BarTender Cloud
- BarTender Cloud – What’s New
- Getting Started with BarTender Print Connector for Microsoft Dynamics
- How to Update Your Client Authentication Apps
FAQs
FAQs
GENERAL
We understand that customers do not all have the same security considerations. By changing our identity provider, we will be able to offer more flexibility and scalability for customized security for BarTender Cloud customers.
BarTender Cloud will introduce Organization Domain IDs to access specific accounts and BarTender Cloud APIs. Each BarTender Cloud account will receive an Organization Domain ID, which will be needed when requesting an access token for users and application types (web, console, service, etc.).
For the first time logging in after the migration, you will receive an email from BarTender Cloud that will provide you with your Organization Domain ID and new account sign-in link. The new sign-in link will be in the form of https://ORGID.account.REGION.bartendercloud.com.
If you are using additional access tokens to connect with any of the BarTender Cloud APIs, they must be migrated before December 31, 2024. Your existing tokens will remain active but any non-migrated tokens will no longer function after this date.
It is required to re-register your BarTender Cloud account. The new Organization Domain ID will change the URL that you use to log in to BarTender Cloud.
By not re-registering your account, you will lose access to BarTender Cloud entirely.
You will be able to re-register your account any time after your region’s scheduled migration date. On the day of your region’s scheduled migration, you will receive an email from BarTender Cloud that will provide you with your Organization Domain ID and new account sign-in link. The new sign-in link will be in the form of https://ORGID.account.REGION.bartendercloud.com.
Please take a moment to review your region’s migration date:
- Sunday, October 6: Asia-Pacific
- Sunday, October 13: Europe, Middle East, Africa
- Saturday, October 19: North America, South America
- 52.33.105.26
- 54.244.69.255
- 44.225.174.104
- 34.217.238.27
- 35.82.91.66
- 44.227.20.62
You will receive your Organization Domain ID via email from BarTender Cloud on the day of your region’s scheduled migration date.
Please take a moment to review your region’s migration date:
- Sunday, October 6: Asia-Pacific
- Sunday, October 13: Europe, Middle East, Africa
- Saturday, October 19: North America, South America
The URL that is displayed when you first sign in to BarTender Cloud indicates which data center (region) your organization uses. Currently, BarTender Cloud is hosted in three data centers whose URLs use regional prefixes, as follows:
- am1.bartendercloud.com: Serves organizations that are hosted in the Americas region
- ap1.bartendercloud.com: Serves organizations that are hosted in the Asia/Pacific (APAC) region
- eu1.bartendercloud.com: Serves organizations that are hosted in the Europe/Middle East/Africa (EMEA) region
Please be sure to check your spam and junk folders in your email inbox to ensure you didn’t miss the email.
If you cannot find the email from BarTender Cloud. You can still re-register your account by using the original BarTender Cloud URL you already use, searching for your Organization, and updating your password.
Yes. The Print Connector for Dynamics 365 Business Central now requires a Client Secret for generating tokens. You can add the client secret by going to the BarTender Setup page in Business Central and entering the information to the Client Secret field in the configuration form. You can find more information on modifying the Print Connector here
Access tokens contain the security credentials for a login session and identifies the user.
An access token is generated when you log into BarTender Cloud and is managed on your behalf during the session. When interacting with web applications that call a BarTender Cloud API, the BarTender Cloud API will use the access token to identify the user making the request, enabling administrators to verify against configured permissions.
The new identity provider maintains the same industry-standard technologies and protocols as the original identity provider while enabling new functionalities to:
- Use individual email addresses across multiple organizations
- Streamline access through Google-supported federated sign-in
- Limit access to specific applications to prevent the use of unauthorized ones by your team
The latest BarTender Cloud release will include the following features & enhancements:
- New enhanced control settings for streamlined printer management, featuring printer-level user permissions, printer groupings, and role-based configurations
- Enhanced print job history capabilities, enabling users to search past print runs by specific criteria and export detailed printer activity logs
- New reprint capabilities, allowing users to reprint individual files with comprehensive logs of all reprinted jobs
- Updated Template Assistant UI including new Embedded Data view to enter and import multiple records at once
- Newly added support for MySQL data sources – Azure DB and Amazon RDS
No, you will need to log out of the BarTender Cloud tenant space and log in to the new BarTender Cloud tenant space you want to access
For technical assistance during or after your identity provider migration, visit the Support Center and get in touch with our technical support team.
APPLICATIONS
Yes. If you are using additional access tokens to connect with any of the BarTender Cloud APIs, they must be migrated before December 31, 2024. Your existing tokens will remain active but any non-migrated tokens will no longer function after this date.
For most client applications, there should be no need to recreate any applications. However, depending on your implementation, there may be some small changes needed for your application requests an access token.
For your reference, please examine the updated sample web application article to learn how to create a BarTender Cloud enabled application. Below is a summary of the changes:
- The scope “user:query” will not be supported by the new identity provider and should be removed. If included in the login, this will result in an error.
- It is possible to convey a fixed Organization Domain ID during the login flow to bypass the Organization prompt.
- The OnRedirectToIdentityProviderForSignOut handler has been changed slightly with a rename of the query parameter used to convey the logout redirect location.
For your reference, please examine the updated sample console application article to learn how to create a BarTender Cloud enabled application. Below is a summary of the changes:
- The scope “user:query” will not be supported by the new identity provider and should be removed. If included in the login, this will result in an error.
- Token requests must include the target Organization Domain ID as any given email address may be used within more than one organization
If you are using the OIDC discovery document approach, your application will continue to work until the current access token it is using expires.
The failure will occur when the application attempts to retrieve a new access token because the scope “user:query” is still being supplied and because the previous password-based authentication sample did not include the now required “OrganizationDnsName” query parameter described previously in this document.
