Release Notes

The changes reported in the release notes are cumulative. All customer-visible functionality updates as well as any known issues and suggested workarounds are included.

Release 2.23.4 (6 May 2025)

Resolved Issues

• Shipment tracking service: An update was implemented in order to increase the accuracy of updating statuses for shipments to India.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.23.0 (24 April 2025)

New Features & Enhancements

• Shipment cancellation notifications: Functionality has been added to notify the Console user of a cancelled shipment so that a new shipment request can be created. The notification message is sent as an email as well as displayed under Notifications in the Console. For multiple cancellations, notification messages are aggregated into a single email.

• Returned shipment notifications: Functionality has been added to notify the Console user of a shipment that has been returned to the sender so that appropriate actions can be taken. The notification message is sent as an email as well as displayed under Notifications in the Console. For multiple return-to-sender notifications, the messages are aggregated into a single email.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.22.0 (27 March 2025)

New Features & Enhancements

• User authentication: When logging in to the Console as a first-time user with Console Owner role in limited “demo mode”, the user has the option to immediately register a YubiKey to get full access to features. This functionality has been updated. After registering a YubiKey, the user is now prompted to re-authenticate using the newly registered YubiKey, thereby leaving “demo-mode” and obtaining full feature access. For more information, see Onboarding.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.21.1 (28 February 2025)

Resolved Issues

• Bulk shipment CSV file: When uploading a CSV file containing incorrect quotation marks, an internal server error was returned instead of a helpful error message. This issue has been resolved, and the error message returned in these cases has been updated to provide informative user guidance.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.21.0 (27 February 2025)

New Features & Enhancements

• Shipment details: To make it easier for users to see which fields have specific data, field names are now displayed for address information in the Shipment details page in the Console. For example, names for “Address line 1” and Address line 2“ are now explicitly displayed to make it easier to see which data each field holds, useful for example when solving address validation issues.

• User management API: organization/users/{email} previously listed as deprecated (May 2024) has now been removed. This has been replaced with users/{user_Id}. For more information, see Users in the YubiEnterprise API Reference.

• Dashboard: To avoid confusion, the product license quantity has been removed from the “Customizations available” section of subscription products on the Dashboard in the Console. Only the various customizations that are available for the particular tier are now displayed.

• Sample email API: The POST /v1/organization/send-sample-email/{template} API has been deprecated and will only be available until September 2025. Shipment notification emails can be managed in the Console, see Notifying About Shipments.

• Shipment CSV upload error message: When a user uploads a CSV to the Console for a bulk upload, the system provides specific error messages if there are errors. However, if the CSV file contains more than 50 errors, no specific error messages appear, making it difficult to understand how to solve the errors in the file. The error message has now been enhanced to provide better guidance and support for resolving the errors.

• Address validation override option: In case of address validation failure for shipments in the Console, an email is sent to the shipment requester. This email has been enhanced to also include information about the Address validation override option.

Resolved Issues

• Inventory allocation issue when editing shipment: Previously a Console user could not edit a shipment request from an inventory without remaining products, even if the user was not adding any products when editing. The shipment request update would fail. This issue has been resolved, and users can edit shipment details for a shipment with no remaining inventory allocation.

• Incorrect link in email notification: The link in the email notifying users about expiring API tokens was pointing to the wrong location. The link has been updated, and is now pointing to the correct location informing users how to regenerate API tokens.

• Notification display issue: When viewing notifications in the Console and clicking a link to view a shipment, there was an issue where the Notification dialog remained on top of the Shipment details page hiding the information. This issue has been resolved and the Notification dialog closes when a user clicks a link to view shipment information.

• License number error in Dashboard: When viewing “Total licenses available” on the Console Dashboard, there was an error where incorrect information was displayed in cases where “0%” should have been displayed. This issue has been resolved, and the correct information is displayed.

• Incorrect setting of “is_delivered” in CSV file: Previously the “is_delivered” column in the CSV file for downloading shipments was set to “false” even if the shipment was in state “Delivered”. This issue has been resolved, and the “is_delivered” column is correctly set to “true” if the shipment status is “Delivered”.

• Incorrect setting of “is_shipped” in CSV file: Previously the “is_shipped” column in the CSV file for downloading shipments was set to “true” even if the shipment was in the “Sent For Fulfillment” status. This issue has been resolved, and the “is_shipped” column is now only set to “true” if the shipment status is at least “Shipped”.

• Empty field after validation failure: When creating a shipment request in the Console, the “Region/State” field in the shipment form was emptied after a fulfillment rule validation failure. The issue has been resolved, and in case of a fulfillment rule validation failure, all shipment information remains as expected.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.20.3 (23 January 2025)

New Features & Enhancements

• Shipment tracking emails: Functionality has been added enabling users to update and customize the email template used when notifying recipients about tracking information changes. In support of this, a new “Tracking Update” option has been added to the email Template dropdown menu available in the Email page in the Console. For more information, see Notifying About Shipments.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.20.1 (17 January 2025)

New Features & Enhancements

• Recipient email reference links: The documentation reference link in the email that the recipient receives when a shipment fails with “Shipment Failure: Address Not Accepted by Carrier”, has been updated. The reference link now points to the specific place in the user guide for user self-service support when solving address validation issues.

Resolved Issues

• Shipment tracking update email issue: An issue was reported where the tracking update email was sent in cases where the shipment status was overridden without actually changing the tracking information. This issue has been resolved, and the tracking update email is now only sent to the recipient if the tracking information is changed.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.20.0 (16 January 2025)

New Features & Enhancements

• Notifications: A new feature has been added to inform Console users of recent activities, for example those requiring user interaction. A Notifications (bell) icon has been added to the top menu in the Console for viewing and managing notifications. For more information, see Viewing Notifications.

• Shipment search API: The /v1/shipments/search-description API previously listed as deprecated (July 2024) has now been removed from the API. The /shipments_exact/search-description API should be used instead.

• Purchase order CSV API: The /v1/purchaseorders/csv API previously listed as deprecated (July 2024) has now been removed from the API. There is no replacement API for this functionality.

• Shipment tracking: Functionality has been added to notify a shipment requestor whenever the tracking information for a shipment changes. For example, if the tracking number or carrier for a shipment is changed, an email is sent to the shipment requestor notifying about the change.

• Table sorting: Functionality has been updated for the sorting of rows in tables on Console pages. Previously the default available sort orders were ['asc', 'desc', null], where “null” would turn off the sorting. To avoid confusing users, the available sort orders have been limited to ['asc', 'desc'].

Resolved Issues

• Issue when selecting Region/State: When creating a single shipment request in the Console, there was an issue when using tab to move to the Region/State field and type in a letter to open the list. This issue has been resolved. Users can now use tab to go to the Region/State field, type in a letter, and select the desired region/state as expected.

• Not possible to enable SSO after an update: When updating the SSO configuration in the Console, the “Enable SSO” button stayed inactive after saving. The button was activated only after reloading the page. This issue has been resolved, and the user can click “Enable SSO” to enable the SSO settings after a configuration update.

• Required fields not highlighted: When creating a shipment request in the Console and leaving required fields empty, the recipient information fields were not highlighted when trying to save the shipment request. This issue has been resolved, and all required fields that are left empty are now highlighted when the user tries to save the shipment request.

• Issue with autocomplete in Region/State field: When creating a shipment request in the Console using autocomplete, this populates the Region/State field dropdown as search text but does not add the actual value. This issue has been resolved, and the actual value is now entered as expected in the Region/State field when using autocomplete.

• Key quantity display discrepancy: An issue was reported where there was a quantity difference between the product listing under Item details, and selected form factors under Product selection in the Shipment details page in the Console. This was due to an error in the handling of line count for multiple items of the same product model for not-yet processed shipment requests. This issue has been resolved, and the correct key quantity is now displayed.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.19.1 (26 December 2024)

Resolved Issues

• SSO and WebAuthn login: An issue was reported where a Console Owner within an organization with Single sign-on (SSO) enabled could not navigate to the SSO configuration page in the Console when logged in using WebAuthn credentials. Instead an “404 Page Not Found” error was displayed. This issue has been resolved, and a Console Owner logged in with WebAuthn credentials can now navigate to the SSO configuration page as expected.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.19.0 (19 December 2024)

New Features & Enhancements

• Shipment address verification - non-Latin characters: When entering addresses in the Console, it was previously possible to use non-Latin characters which caused issues where carriers were unable to print the addresses. To avoid these issues, functionality has been added preventing users from entering non-Latin characters for shipment addresses. If non-Latin characters are used, the shipment is not accepted and an error message is displayed informing the user that non-Latin characters cannot be used.

• Shipment address verification - postal codes: When entering addresses in the Console, the postal codes for shipments to the US are now validated for the correct format to avoid shipping issues. The postal code entered in the shipment request must be in either the 5-digits (12345) or 5+4 digits (12345-6789) format. If the postal code format is incorrect, the shipment is not accepted, and an error message is displayed informing about the correct format to use.

Resolved Issues

• Error message missing for shipment request without products: When correcting addresses for shipment requests with validation errors in the Console, it was possible to submit the corrected request even though the product quantity was zero. Only when the user clicked the back button in the form was an error message displayed. This issue has been resolved and the “Shipment has no shipment items” message is now correctly displayed when trying to submit the form without specifying a product quantity.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.18.1 (3 December 2024)

New Features & Enhancements

• Shipment request bulk deletion: Functionality has been added to the All shipments page for bulk deletion of shipments with status “Address not Supported by Carrier”. Console users can now filter out shipments with this status and apply bulk deletion to the selected shipments.

Resolved Issues

• Shipment destination country selection issue: In some cases the Region/State field in the shipment request form in the Console was not allowing input if a country other than the US or Canada was selected. This happened even though the organization had other countries enabled. This issue has been resolved and users are now able to select countries as expected.

• Unable to delete shipments: Previously in some cases users were unable to delete shipments with status “Awaiting DPL Verification” in the Console. This issue has been resolved and shipments with this status can be deleted as expected.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.18.0 (2 December 2024)

New Features & Enhancements

• Shipping to multiple addresses (bulk shipments): When creating a shipment request to multiple addresses in the Console, users can now select products from customized inventory, and customization IDs are displayed in the product selection.

• Purchase orders: Customization support has been added to purchase orders for both FIDO Pre-reg and non-FIDO Pre-reg type of customizations. A new column has been added to the Purchase order pages in the Console displaying Customizations IDs where applicable.

• Dashboard: The Console dashboard layout and functionality has been updated for a better user experience. Support for customizations has been added to display availability of customized inventory. The display of inventory and associated form factors has been updated for a clearer view of availability. The “Only show shippable inventory” toggle is now set to on “On” by default. The display of primary/secondary subscriptions and create shipment request options have been enhanced to make it easier for users to select the right inventory.

• Shipment tracking: Functionality has been added to improve tracking of shipments sent to India. When a shipment has arrived in India, a status email with updated information about carrier, tracking number, and tracking service is sent to the shipment requestor.

• Shipment request confirmation: When creating a shipment request, the information on the confirmation page has been updated to provide a more complete overview of details. The information includes display of address validation override selection, product names and selected form factors, and any customizations applied.

• Shipment recipient address: The support for using non-latin characters in the shipment recipient address has been removed. The reason for this is to avoid issues where carriers are not able to print address labels with non-latin characters. If entering non-latin characters when creating a shipment request (Console and API), an error message is displayed and the address fails the address validation. Accented characters (à, á, ä etc.) are still permitted.

• Product selection: When creating shipment requests in the Console, the product selection has a new design for improved usability. Also, functionality has been added making it possible to select both customized and non-customized products form an inventory (FIDO Pre-reg type of customizations are excluded since these shipment requests are not created in the Console).

• Products API: The GET /v1/products API has been updated to return customization_id in the products payload. The field was already available but was previously set to return null.

Resolved Issues

• Inventory allocation issue when editing shipment: Previously a Console user could not edit a shipment request from an inventory with no remaining keys. Editing was not possible even if the user was not adding any products when editing, and the shipment request update would fail. This issue has been resolved, and it is now possible to edit shipment details for a shipment with no remaining inventory allocation.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.17.8 (14 November 2024)

New Features & Enhancements

• Filtering of shipments: The functionality for filtering shipments in the All shipments page has been updated. Shipment requests that failed due to address length limitations will be displayed with status “Address Not Accepted by Carrier” in the list of shipments. A filter has been added for this status in the advanced search so users can filter out shipments that failed due to address length limitations.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.17.7 (14 November 2024)

New Features & Enhancements

• Shipment notifications: The functionality for sending shipment notification emails to recipients has been updated. Email notifications for address validation errors involving long street names in shipment addresses were not sent out. Also, the shipment history message in the email was incorrect. This has been updated and the correct email notifications are now sent out for this type of address validation errors.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.17.6 (13 November 2024)

New Features & Enhancements

• Shipment recipient addresses: The handling of long shipment recipient addresses has been updated. In cases where the shipment address is longer than what is accepted by the YubiEnterprise Delivery service and associated carriers, the shipment will fail validation with status “Unable to format shipment address”. An email is sent notifying the requester about the failure, informing them that the shipment request needs to be updated with a shorter address. If the destination country is India, 120 characters can be used for Address line 1 and 2 in the Console shipment request form. For other destinations, 105 characters can be used. Address validation override cannot be applied for this type of validation failure.

Known Limitations

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.17.0 (24 October 2024)

New Features & Enhancements

• Sorting of customizations: Sorting has been added to the table on the Customizations page. Console users can now sort the table by “Customization ID” or “Status” to make it easier to locate a specific customization.

• Updated column header name: In the Users page in the Console, the table column header previously named “Edit” has been changed to “Actions” to align with other tables of similar type. This column displays the different actions, for example edit or delete, that can be performed for an item.

• Search filter enhancements for shipments: To help Console users locate a specific shipment, the granularity of filter options has been improved in the table on the All shipments page. Users can now filter on for example recipient first name and last name, address line 1, and city and state.

Resolved Issues

• Notification emails sent to suspended accounts: Previously when notifying recipients about shipment delivery exceptions, the notification email was also sent to suspended (inactive) users in an organization. This issue has been resolved, and notification emails are now only sent to active users.

• Issues when moving table columns: In some Console pages it was not possible to change the display order of columns. When trying to drag and drop a column to a different place it would not snap into the desired position. The problem appeared in for example the Purchase orders, Users, and Processed refunds pages. This issue has been resolved and moving columns now work as expected in these pages.

• Form factor display text is cut off: When expanding the content for a subscription card on the Dashboard in the Console, the display text for form factors with long names are truncated. This makes it difficult to understand which form factor is available. This issue has been resolved, and the display has been adjusted so the entire form factor text is visible.

Known Limitations

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.16.3 (23 September 2024)

Resolved Issues

• Error when resetting user in Console: An error message was displayed when a user was trying to reset another user in the Settings page. This issue has been resolved, and resetting users for an organization now works as expected.

Known Limitations

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.16.1 (13 September 2024)

New Features & Enhancements

• Shipment CSV downloads: The functionality for downloading CSV files with shipment requests from the All shipments page has been enhanced, and it is now possible to download large data files. When downloading a large data file, a message is displayed informing the user that due to the size of the request, generation of the download CSV file might take some time to complete.

Known Limitations

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.16.0 (12 September 2024)

New Features & Enhancements

Address validation override - Console updates:

• Console users now have the option to override the system address validation from the All shipment and Shipment details pages for shipments that failed due to address validation error. When overriding the address validation, a confirmation message is displayed informing users of potential consequences such as additional costs. For more information, see Overriding Address Validation.

• Console users now have the option to override the system address validation when creating single or multiple shipment requests. Checkboxes have been added in the shipment creation forms that when selected will bypass the address validation for the shipment. Confirmation messages have been added informing users of potential consequences such as additional costs when bypassing the address validation. For more information, see Shipping to a Single Address and Shipping to Multiple Addresses: Bulk Shipments.

• When performing address validation override for a single shipment in the Console, the confirmation dialog displays the address fields for the associated shipment. The information is displayed both when creating and editing a shipment.

• When performing address validation overrides for multiple shipments at the same time in the Console, a confirmation dialog has been added. The dialog informs users of potential consequences such as additional costs when overriding the address validation. For more information, see Overriding Address Validation.

• Support for different address validation override scenarios has been added when editing a shipment request. For example, if address validation override was previously applied for a shipment, the address validation override checkbox is pre-selected when editing the shipment. Also, the address validation override option is enabled or disabled depending on the state of the shipment.

• A new column displaying whether address validation override has been applied for a shipment has been added to the table in the All shipments page in the Console. A new filter option has been added allowing users to filter out shipments with address validation override. If address validation override was applied for a shipment, this is clearly indicated in the Shipment status section of the Shipment details page.

• When shipments fail due to address validation errors, email notifications are sent for each of the failed shipments, to the user that created the shipment. These email notifications are now grouped before being sent, to reduce the amount of emails.

• The CSV file on the All shipments page in the Console has been updated to include a field for address validation override. This information allows users to for example perform data analysis on shipment validation failures. For more information, see Downloading List of Shipments.

Address validation override - API updates:

• New API endpoints have been implemented that supports performing address validation overrides on multiple shipments. The shipment update and creation APIs have been updated to indicate whether the default address validation should be overridden. If address validation is overridden, the shipment will still undergo DPL validation. For more information, see the YubiEnterprise API docs.

• The /shipments_exact API endpoints (including shipment details sub-routes) have been updated to include address validation information. A boolean field has been added indicating if address validation was overridden for a shipment.

• An address_validation_bypass field has been added to the API to indicate shipments where address validation was overridden during create. The /shipments_exact endpoints (including shipment details sub-routes) now return shipments with address_validation_bypass set to true for these shipments.

• API support has been implemented for address validation override when uploading a CSV file to create multiple shipment requests at the same time. A flag has been added indicating that address validation will be skipped for all shipments in the CSV file.

• The shipment create and update APIs for FIDO Pre-reg shipment types have been updated to indicate whether the default address validation should be overridden. If address validation is overridden, the shipment will still undergo DPL validation.

Other updates:

• Console table column ordering: When a user changes the order in which columns are displayed in tables, the updated order preference is preserved so the user does not have to re-order columns again on next login. The enhancement applies to all pages with tables in the Console.

• Date and time display: The format for display of date and time in the Console has been unified for a more consistent user experience. The date and time format is now localized based on the user’s timezone, for example Jul 2, 2024, 09:48 AM MST (US) and 2 juli 2024 09:48 GMT-7 (Sweden). The update applies to all instances within the Console.

• Product name change: To enhance the user experience, “Standard product” has been renamed to “Physical product” in all instances in the Console. A physical product refers to keys and lanyards, as compared to subscriptions and tiers.

Known Limitations

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.15.4 (26 August 2024)

Resolved Issues

• Wrong company name on shipping label: The customer’s organization name instead of the recipient’s company name was printed on the shipping label. This issue has been resolved, and the recipient’s company name as entered by the customer in the shipment request is now printed on the shipping label.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.15.0 (15 August 2024)

New Features & Enhancements

• Console login: Functionality has been added to enforce expiration of one-time tokens used during login. Previously when a user received an email with a reset link (one-time token), and then reset their login again, another email with a login link was sent while the one in the previous email was still valid. Each link would expire 7 days after creation. With the new functionality, any new user reset invalidates links in previous emails and only the link in the last email can be used.

• Create shipment error handling: Error handling when creating shipments has been improved so that users do not have to correct errors one by one during repeated submissions of the create shipment form. If there are multiple errors or missing data in required fields in the form, incorrect fields are now clearly highlighted upon the first submission of the form.

• Shipment bulk deletion: Deletion of multiple shipments can now be done directly in the All shipments page through a new multi-select feature. Only shipments with certain statuses can be selected for deletion. A quick filter has been added to filter out shipments with statuses allowing them to be deleted.

• Bulk shipment CSV file processing: The processing of uploaded CSV files when creating multiple shipment requests (bulk shipments) has been improved to avoid the creation of duplicate shipment requests. If a file with the same set of addresses as a previous file is uploaded within the last 90 days, a notification is displayed to the user informing about the duplicate upload.

• Address validation failed status name: The status message displayed to users when the address validation failed for a shipment was unnecessarily verbose and confusing. Therefore the status message has been changed from the previous “Address is undeliverable or could not be understood” to “Address Validation Failed”. The change applies to both new and existing shipments with address validation failures. The status code (7) has not been changed, only the message.

Resolved Issues

• Inactive products available for selection: Previously when creating a shipment and selecting products, in some cases products that had been inactivated still appeared available for selection. This issue has been resolved, and inactive products are now filtered out and are not available for selection.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.14.3 (25 July 2024)

Resolved Issues

• Inventory error: In some cases certain shipments that included custom-programmed keys were incorrectly receiving an insufficient inventory error. This issue has been resolved, and fulfillment of these shipments now works as expected.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.14.2 (23 July 2024)

Resolved Issues

• Incorrect tracking links: In some cases, incorrect tracking links were displayed for shipments handled by Yubico in-house fulfillment. Instead of displaying a tracking link to the associated carrier, the tracking link was pointing to a generic search for the specific tracking number. This issue has been resolved, and the tracking link now correctly points to the tracking page of the associated carrier, if this is known.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.14.1 (22 July 2024)

Resolved Issues

• Broken links to contact Yubico Support: The path for the “Contact Yubico Support” link was changed from /yubienterprise-subscription/ to /yubikey-as-a-service/ which caused some links in the YubiEnterprise Console user interface and the user guide to break. This issue has been resolved. The “Contact Yubico Support” links have been updated to the correct one in all instances and are now working properly.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.14.0 (18 July 2024)

New Features & Enhancements

• Customizations: Console Owners can now add user-friendly Customization labels to Customization IDs to make it easier to identify specific customizations and understand what they include. Customization labels can be added and updated, and shared between multiple organizations. Console users can view Customization labels, but only Console Owners can add and edit them. For more information, see Adding Customization Labels.

• API: The following APIs previously listed as deprecated, will be removed:
  • /shipments. Use /shipments_exact instead.
  • /shipments/bulk. Use the Console user interface instead.
  • /shipments/bulkvalidate. Use the Console user interface instead.
  • /shipments/{shipmentId}. Use shipments_exact/{shipmentId} instead.
  • /address-validation. Use /validate-address instead.
  • /shippablekeys. Use GET /v1/inventory and GET /v1/products instead.

For more information, see Deprecated APIs: Overview and the YubiEnterprise API documentation.

• API: Additional validation has now been added to the Create FPR Shipment API to verify that the FIDO2 encrypted requests use a valid Transport Key ID. Requests with an invalid Transport Key ID will fail during shipment creation with a “400 Bad Request” error.

• Customizations: Customization labels (friendly names) have been added to the details for Refunded shipments to make it easier to identify the customized inventory associated with a refund. If no Customization label exists for a customization, the Customization label column is empty.

• Customizations: Customization labels (friendly names) have been added to the Shipment details page to make it easier for users to understand which customizations are associated with a specific shipment. If no Customization label exists for a customization, the Customization label column is empty.

• Customizations: An audit log feature has been added so that Console users can view the changes to customization labels (friendly names). A change history icon has been added to the Actions column in the Customizations page. The history information includes the date when a change was made, the updated customization label, and the email of the user that made the change. For more information, see Customizations.

• API: The listShipmentSearchDescription API has been deprecated and will only be available until January 2025. The /shipments_exact/search-description API should be used instead.

• API: The deprecation messages for the deprecated /organization/users and /organization/users/{email} APIs previously displayed under the Request Body Scheme section have been moved to the Title section in the API documentation.

• API: A deprecation message for the /organization/users/search-description API planned to be removed starting November 2024, has been added in the API documentation.

• API: The /purchaseorders/csv API is being deprecated and will only be available until Jan 2025. There is no replacement API for this functionality.

Resolved Issues

• Disabled product filtering: Previously when a product had been disabled for an organization, the product would not be available on the dashboard or when creating a single shipment but would still appear in the bulk shipment CSV template for the organization. If using the column for a disabled product when creating a bulk shipment, the request would be rejected due to an invalid product ID. This issue has been resolved and disabled products are filtered out.

• Console Owner role change: In cases where there was only one Console Owner for an organization, it was possible for this user to change their own role to for example Console Admin. Doing this removes the ability to manage organization users as only Console Owners can add and delete users. This issue has been resolved. If there is only one Console Owner for an organization, they cannot change their role without adding at least one other Console Owner first.

• Tracking status: Previously the “coming soon” tracking status for the shipping provider was displayed as a clickable link pointing to an irrelevant website. This issue has been resolved, and the hyperlink has been replaced with plain text in all places where it was displayed, including the Shipment summary table, the CSV file export, bulk shipment operations, and Shipment details.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.13.0 (20 June 2024)

New Features & Enhancements

• Console: The user interface components in the Console have been updated. The updated version includes performance improvements, new table column selection with reset option, and updated date picker when searching and filtering table data in pages.

• Download shipments: The is_fido_preregistered column has been removed from the CSV download file. This column is not needed since FIDO Pre-reg shipments are already included in the shipment type column when downloading shipment data.

Resolved Issues

• Processed refunds: When displaying refunds on the Processed refunds page in the Console, there was a mismatch between the number of rows in the table and the page size set in the pagination. In some cases, the table contained fewer rows than the total number of rows as defined in the pagination setting. This issue has been resolved, and the total number of displayed rows as set in pagination is now correct.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.12.0 (6 June 2024)

New Features & Enhancements

• Console: The “Customization” page and its navigation links were renamed from “Customization IDs” to more accurately reflect the content of the page. For more information, see the new Customizations section in the Console guide.

• Console: When downloading a CSV file with shipments in the All shipments page, the user is notified when trying to download a file that is greater than the download limit (50,000 records). When hovering over the download button, a notification is displayed informing the user that they should refine their search because the download file contains too many rows.

• API: Support has been added to include serial number and firmware version in the CSV file when downloading shipments from the All shipments page. New columns for description, quantity, cost, serial number and firmware version have been added for each physical product. Serial number and firmware version are only displayed for FIDO Pre-reg shipments.

Resolved Issues

• Console: Previously when a user’s password was reset, the session was not properly terminated. This issue has been resolved. When a user’s password is reset, all sessions belonging to the user whose password was reset, are destroyed. The next time the user interacts with the Console, they will be asked to log in again.

• Console: A user was initially invited to the Console through an email containing a mix of uppercase and lowercase letters. When the same user with the same email address was invited again, the email contained only lowercase letters which caused the system to consider the user as new, requesting a login creation. This issue has been resolved and case-insensitive checks have been added.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.11.0 (23 May 2024)

New Features & Enhancements

• Console: The serial number and firmware version for pre-registered keys in FIDO Pre-reg shipments (Limited Early Availability service) can now be viewed in the Shipment details page. When clicking Details in the new Action column, a list with serial numbers and firmware for the selected inventory is displayed. The list supports pagination.

• Console: Support has been added for searching on pre-registered keys (FIDO Pre-reg Limited Early Availability service) associated with specific serial numbers or firmware versions in the Console. Filters for serial number and firmware version have been added to the advanced search functionality.

• Console: Support has been added to view Customization IDs associated with shipment of custom keys in the Console. A Customization ID column has been added in the Item details section of the Shipment details page. The information is only visible if a shipment contains customized inventory.

• Console: A Customization IDs page has been added to the Console so that users can view all Customization IDs associated with their organization. The Customization IDs are displayed together with information about the status of the customization to show if it is in use. The Customization IDs page is only visible if an organization has associated Customization IDs.

• Console: The table headers in the Console have been enhanced. When displaying more than 25 rows in any table, the table header will remain visible at the top when scrolling down on a page, making it easier for users to understand the column contents.

• API: The User management API has been updated. New endpoints are introduced replacing the existing one, some endpoints have moved, and a new endpoint has been added. Previously the User management API was including the email of the user in the path parameter. The endpoints have been changed to include the user ID instead of the email address.

The following endpoints have been replaced:

• Change user role:
  • Old: POST /v1/organization/users/reset/{email}
  • New: PUT /v1/users/{userId}; body {"roles": ["org-owner","distributor","reseller"]}
• Reset user account:
  • Old: POST /v1/organization/users/reset/{email}
  • New: POST /v1/users/{userId}; body {"action": "reset-user"}
• Reset user password:
  • Old: POST /v1/organization/users/reset-password/{email}
  • New: POST /v1/users/{userId}; body {"action": "reset-password"}
• Delete user:
  • Old: DELETE /v1/organization/users/{email}
  • New: DELETE /v1/users/{userId}

The old endpoints are deprecated and will be available until November 23, 2024.

The following endpoints were added or moved:

• Gets one user for an organization:
  • New: GET /v1/users/{userId}
• Gets all users for an organization:
  • Old: GET /v1/organization/users/
  • New: GET /v1/users/
• Returns a list with searchable user fields:
  • Old: GET /v1/organization/users/search-description
  • New: GET /v1/users/search-description
• Creates new user for an organization:
  • Old: POST /v1/organization/users/
  • New: POST /v1/users/

For more information, see the YubiEnterprise Delivery API documentation.

• Console: A shipment’s delivery type (Normal or Expedited) for shipments of pre-registered keys (FIDO Pre-reg Limited Early Availability service) can now be edited on the Shipment details page. FIDO Pre-reg shipments can be edited in the same states as for automated shipments.

• Console: It is now possible to view Customization IDs associated with purchase orders for custom keys in the Console. A column has been added in the Products section of the Purchase order details page, displaying the Customization ID and its status (whether it is in use or not). The information is only visible if a purchase order contains customized inventory.

• Console: Users can now view Customization IDs associated with refunded customized shipments for their organization. A column displaying Customization IDs has been added to the Refunds section of the Shipment details page.

Resolved Issues

• Console: In the Shipping section on the Shipment details page in the Console, information is displayed about the shipping provider and tracking. Previously the status “coming soon” appeared as a clickable link pointing to an irrelevant website. This issue has been resolved, and the hyperlink has been removed.

• Console: When entering a login URL with a leading space in the SSO configuration form for an identity provider, the URL was not validated. This issue has been resolved, and the entered login URL is now properly validated.

• Console: A user with Console Owner role for an organization issued a machine token for authentication. The user’s role was then changed to Distributor (Distributor Role). After this role change the user was still able to use the previously issued machine token. This issue has been resolved. When roles in an organization are updated for a user, and the new role is not Console Owner or Console Admin, any machine tokens issued by the user will be removed.

• Console: Previously when clicking Create shipment request from an inventory card on the Dashboard, the create shipment form was empty instead of being pre-filled with information from the clicked inventory source card. This issue has been resolved. When creating a shipment request by clicking a card on the Dashboard, the Reseller and Product selection fields are pre-filled.

• Console: A shipment request was placed for a license that the organization no longer had inventory for. The shipment was accepted even though there was no inventory, and the shipment remained in status “Accepted for Fulfillment”. This issue has been resolved, and a shipment request will fail during processing if there is no available inventory.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.10.3 (25 April 2024)

Resolved Issues

• Previously when creating a shipment request in the Create new shipping request page, the “Shippable count” was not displayed if the remaining allocation was less than the subscription amount for a form factor. Because “Shippable count” is also used for displaying the amount of customized keys available for shipping, this caused inconsistency in the display of the amount of shippable keys. This issue has been fixed. If a form factor has an inventory allocation, “Shippable count” is always displayed when selecting products for a shipment request.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.10.0 (11 April 2024)

New Features & Enhancements

• API: The update shipment validation has been updated to support customization ID and customizable inventory. BasicShipmentValidation now verifies the following:
  • The customization has includes_fpr flag set to true.
  • The product_id product’s corresponding shippable item has is_custom flag set to true.
  • The validate-by-partner check verifies that a partner is configured for FIDO Pre-reg or any shipment type for that organization.

• Console: The contact support link in the Console and the login page has been updated to reduce the number of clicks a user has to take to submit a support request. When clicking the support link, users are now taken directly to the YubiEnterprise Delivery support page with the support form opened. Previously a user had to click to open the form to enter data.

• API: validate-address has been updated to support shipments of type Auto FIDO Pre-reg (pre-registered keys). This API is used to verify addresses for shipments of pre-registered keys as part of the fulfillment process.

Resolved Issues

• API: When calling the POST endpoint /v1/organization/users/reset/valid.email@yubico.com in a scenario where the user does not exist in the organization, the API was incorrectly returning a 500 error. This issue has been resolved and the API returns the correct 404 error.

• API: When calling the POST endpoint /v1/organization/users/reset/invalid-email in a scenario where the user’s email is invalid, the API was incorrectly returning a 500 error. This issue has been resolved, and if the user’s email is invalid the API now returns a 400 error.

• API: When calling the POST endpoint /v1/organization/users/reset/valid.user@yubico.com in a scenario where the user had been suspended and had a + sign in their email, the API was incorrectly returning a 500 error. This issue has been resolved. The suspended user is reset and the API returns the correct 200 error.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.9.2 (29 March 2024)

Resolved Issues

• Inability to edit shipment request: When a user attempted to edit a shipment request which (a) contained standard products inventory and (b) failed validation for a reason unrelated to inventory, the original standard products selection was pre-populated and could not be changed. This was caused by the inventory becoming unavailable between shipment request creation and the moment when the user attempted to modify the request. This issue has been resolved and inventory that has become unavailable in the meantime no longer pre-populates the form.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.9.0 (14 March 2024)

New Features & Enhancements

• Console: The Shipment details page has been reorganized to make better use of available space. The shipment, status, recipient, and item details information is presented in clear sections, and a new status progress bar is added for better overview.

• Console: The click behavior of the left navigation menu in the Console has been aligned for a more consistent user experience. Clicking on a parent menu item expands the section to display sub-items if these exist. A sub-item must be clicked on to display its page content.

• Console: To make it easier for users to navigate the YubiEnterprise Console, all pages now have page headers. These are located under the breadcrumb navigation at the top, informing users what page in the structure they are currently on.

Resolved Issues

• Console: When editing an automated shipment with inventory from a subscription or virtual product with inventory allocation “0”, the form factor quantity field was prefilled with the original quantity but could not be edited. This issue has been resolved, and the field can now be edited.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.8.4 (7 March 2024)

Resolved Issues

• Console: Shipment address validation was failing for FIDO Pre-registered shipment types (Limited Early Access feature) even if the address was correct. This issue has been fixed and the address validation for FIDO Pre-registered shipment types is now working as expected.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.8.3 (6 March 2024)

Resolved Issues

• Console/bulk shipments: When creating a shipment request and submitting a valid bulk shipment CSV file, a success message was displayed. However, due to a validation failure the shipment was not actually being generated. This issue has been resolved, and bulk shipment requests are successfully validated and generated.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.8.1 (22 February 2024)

Resolved Issues

• Console/bulk shipments: Uploading a CSV address file containing an incorrect column header caused an error displaying a misleading and uninformative message. This issue has been fixed. Should you submit a file with an incorrect header, the error message displayed is now correct and more helpful.

• Console: The Address line 3 field used when creating shipment requests was removed in release 2.8.0. However, the field still appeared in some instances when editing shipments. This issue has been fixed and the Address line 3 field is removed.

• API: Following the removal of the Address line 3 in forms (release 2.8.0), the corresponding street_line3 field in all parts of the API documentation where this field appears have been marked as deprecated. API responses continue to support street_line3 for existing shipments and purchase orders that contain this information.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see SSO: Known Limitations.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.8.0 (15 February 2024)

New Features & Enhancements

• Console/API: The Address line 3 field in the shipment creation form has been removed for all countries. Following this removal, the corresponding street_line3 field in the shipment API will be deprecated. The field will only be available until September 2024, and there is no replacement functionality.

• Console: You can now conveniently access the functionality for managing your credentials by clicking on your user name in the upper right corner of the page when logged in to the Console. This also provides quick access to log out. The Profile page where this functionality previously existed has been removed. For more information, see Managing Your Account.

• Console: The page footer has been updated. The Yubico logo is removed, and the footer size has been reduced to take up less space. The footer is no longer “sticky” meaning that you only see the footer when you have reached the end of a page.

• Console: The behavior of the left menu navigation is enhanced. You can now collapse and expand the menu by using the [ key, as well as by hovering over the menu with the mouse. The entire list of a user’s organizations is now displayed without the need of vertical scrolling.

• Console: You can now conveniently access the functionality for managing API tokens from the dropdown menu at the top of the left menu. The Profile page where this functionality previously existed has been removed. For more inforamtion, see Generating API Tokens.

• Console: To highlight the recent important changes to the bulk shipment flow and the new CSV templates, a login banner message has been added to the Console. The message notifies about the changes, and provides a link to Shipping to Multiple Addresses: Bulk Shipments in the Console user guide for supporting information.

Resolved Issues

• Console: The role selector at the top of the left menu was showing the wrong color for Distributor and Reseller roles when these were selected. This issue has been resolved and the correct colors are now rendered for all roles when selected.

• Console/account management: A user had MFA registered for their account, and the password was reset but the password reset email was lost. The password was reset again but this time no email was sent. This issue has been resolved. When resetting passwords, any existing reset tokens are discarded, and a new email with a password reset link is sent to the user.

• Console: When trying to delete shipments that failed because of insufficient allocated inventory, this was not possible. This issue has been resolved, and you can now delete and resubmit these failing shipment requests once more inventory is allocated.

• Console: When selecting an organization at the top of the left menu, long organization names were truncated and could not be read. This issue has been resolved and you can now read the full organization name when switching organizations.

• Console: Following the removal of the Address line 3 field in the shipment creation form, the address template CSV file for creating bulk shipments no longer includes a column for Address line 3. Ensure to always download new template files when creating a bulk shipment request.

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.7.0 (18 January 2024)

New Features & Enhancements

• The list of countries supported by YubiEnterprise Delivery has been very substantially extended for single key shipments. The newly available countries are:

  • Albania
  • Argentina
  • Bosnia and Herzegovina
  • Brazil
  • Colombia
  • Costa Rica
  • Dominican Republic (the)
  • Egypt
  • Guatemala
  • Guernsey
  • Isle of Man
  • Jamaica
  • Jersey
  • Malaysia
  • Montenegro
  • Pakistan
  • Panama
  • Peru
  • Puerto Rico
  • Serbia
  • South Africa
  • Korea (the Republic of)
  • Turkey

  The full list of countries available is in the YubiEnterprise Delivery Price list.

  Please contact Support if your organization is interested in enabling any of these countries for single-key shipments.

• Console: Account security - new functionality has been added so that when a security key is removed or added by a user for an account, or when a password is changed, an email is sent to the user. The email informs about the security-related changes, allowing the user to take actions if needed.

• Console: Organizations - if you manage more than one organization, you can now quickly switch between them through a new menu available right next to the organization name at the top. Previously you had to navigate to your Profile page and select a different organization from there.

• Console: Bulk shipments - the process has been improved to make it easier when creating shipment requests to multiple addresses. The CSV template for uploading recipient information has been simplified and products can now be selected in the Console, and from all available inventories. For more information, see Shipping to Multiple Addresses: Bulk Shipments.

• Console: Previously when logging in to the Console, a notification about the recommendation to add more Console Owners was shown to all users, regardless of whether the user’s organization hade multiple Console Owners or not. This notification has now been adjusted so that only users belonging to organizations with a single active Console Owner will see the notification.

• Console: When creating shipment requests, some of the country names have been changed to match the ISO 3166 standard for country codes. For example, “United States” is renamed to “United States of America (the)”, and “United Kingdom” is renamed to “United Kingdom of Great Britain and Northern Ireland (the)”. You can see the new names for example when creating shipment requests and selecting destination countries.

• API: Starting with release 2.7.0, the APIs for bulk shipment requests will be deprecated. The deprecated APIs will be available only until June 2024. From July 2024, the only method for submitting bulk shipment requests is to use the YubiEnterprise Console. The following APIs will be removed:
  • POST /v1/shipments/bulk
  • GET /v1/shipments/bulk
  • POST /v1/shipments/bulkvalidate

Resolved Issues

• Inventory/From Stock: The option to specify the inventory to draw from was not available when using the CSV file with the API or when creating bulk shipments. This issue has now been resolved by the implementation of the new bulk shipment process in release 2.7.0.

• Console: When creating bulk shipment requests and uploading the CSV file, the validation processing was slow and sometimes took too long, causing the browser to time out. The issue was caused by a performance problem which has been resolved.

• Console: When onboarding the Console for the first time as a demo user, a notification about the recommendation to add more Console Owners was shown. However, users in demo mode are not permitted to take the actions described in the message. This issue has been resolved, and demo users will now see a different message.

• Shipment fees: The flat $65 fee for single-key shipments that should have been applied to the following territories and countries is not being applied correctly.
  • US:
    • American Samoa
    • Guam
    • Federated States of Micronesia
    • Marshall Islands
    • Northern Mariana Islands
    • Palau
    • Puerto Rico
    • The U.S. Virgin Islands
  • International:
    • • French Guiana: maps to France (FR) country code
    • Guadeloupe: maps to France (FR) country code
    • Saint Martin (French part): maps to France (FR) country code
    • Martinique: maps to France (FR) country code
    • Réunion: maps to France (FR) country code
    • Jersey: maps to United Kingdom (GB) country code
    • Isle of Man: maps to United Kingdom (GB) country code
    • Guernsey: maps to United Kingdom (GB) country code

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

• Address entry - postal codes: Several countries supported by YubiEnterprise Delivery do not use postal codes (for example Hong Kong, United Arab Emirates). However, postal codes are required  when creating a shipment request, so a request without a postal code will not be successful. Workaround - For shipping to countries without postal codes, enter 00000 in that field.

Release 2.6.8 (8 January 2024)

Resolved Issues

• Console: When creating a shipment request, entering a region/state was also required for countries other than the US and Canada, when selecting a destination country. This issue has been fixed, and region/state is now only required when selecting the US or Canada as destination country.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.6.7 (8 January 2024)

Resolved Issues

• Console: When submitting a shipment request, the country in the address field was changed to the US as default, even if the country originally entered was a different one. This has been fixed, and the correct country is now applied when submitting a shipment request.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.6.2 (7 December 2023)

Resolved Issues

• API: A change introduced in release 2.6.0 slightly altered the sorting functionality, breaking backwards compatibility. The correct behavior has now been restored.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.6.1 (7 December 2023)

Resolved Issues

• API: Support for filtering on integer fields using the exact operator when performing advanced search was accidentally removed in release 2.6.0. The correct behavior has now been restored.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.6.0 (7 December 2023)

New Features & Enhancements

• Console: Customers, distributors and resellers can now get a clearer view of how many products are available for shipping. If there is an allocation set for a specific product due to limited availability, a notification showing the number of allocated shippable products is displayed on the Dashboard and when accessing the Create Shipment Request form. Users are prevented from creating shipments when their inventory selection exceeds their available shippable inventory. For more information, see Shippable Inventory.

• Console: The Edit Shipment functionality has been enhanced by improved design. For more information, including screenshots, see Editing or Deleting Shipments.

Resolved Issues

• Console: The NetSuite sales order number field in the Purchase Order details page has been removed, as the information was superfluous.

• Console: In the Distributor and Reseller views of the Purchase Order details, the Distributor ID line was shown. Since it is not used in any workflows, the line has been removed.

• API: The API documentation has been updated for the shipments_exact APIs to indicate that the shipped_date and delivered_date fields are nullable.

• In rare situations, the tracking_link field for Royal Mail shipment details was not being populated. This issue has now been fixed.

• API: Because the enum subscription_type should be included in the response for GET /v1/products, the subscription_type field has been added to the /products API.

• Console and API: When creating a shipment request, the total number of selected form factors cannot exceed the shippable count. This prevents users from creating shipment requests that would otherwise fail due to insufficient allocation. For more information, see Shippable Inventory.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.5.1 (31 October 2023)

Resolved Issues

• Console: The search results generated by using the Console’s search function to filter on shipments were not the same in the GUI as they were in the downloaded CSV file. For example, filtering shipments by Shipment address with multiple string terms, each separated from the next by a space, as in contains: stockholm 1 might have shown 60 shipments in the Console UI, but the downloaded CSV file would have contained none at all. This issue has now been fixed, and the results displayed by the Console UI are accurately reflected in the downloaded CSV file.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.5.0 (26 October 2023)

New Features & Enhancements

• Console Organizations now receive notification to add at least one more Console Owner if they currently have only a single owner. Console Owner is the only role that can perform password and account resets for users who have been locked out. Organizations that have only a single Console Owner who locks themselves out or leaves the organization will be obliged to contact Yubico to set up a new Console Owner.

Resolved Issues

• API: When getting a purchase order by its ID, extra, undocumented fields were returned. When a request for GET /v1/purchaseorders/{purchaseorderId} was sent, the response included (is_vat_valid, is_tax_exempt, is_post_pay). These extra fields are no longer returned.

• The country name “Vietnam” was wrongly spelt as two words, “Viet Nam”, in several locations, such as in the list of countries to which an organization could ship, and in the shipment creation process. This issue has now been fixed, and “Vietnam” is no longer listed as two words.

• Console: On the Settings tab, the Email field for adding new members is now limited to 255 alpha-numeric characters. This limit applies when adding a new user or editing an existing user.

• API: The public API documentation has been corrected to reflect our implementation for shipment APIs. The following were strings in the public API documentation; they have now been corrected to integer<int64>.

  • shipment_product_cost,
  • shipment_product_taxes,
  • shipment_product_vat,
  • shipping_service_cost,
  • shipping_service_taxes,
  • shipping_service_vat,
  • total_shipment_product_cost,
  • total_shipment_tax_cost,
  • total_shipment_vat_cost,
  • total_shipping_service_cost,
  • total_keys_shipped.

  Similarly, the shipment_destination_vat_rate was a string in the public API documentation; it has now been corrected to number<double>.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.4.3 (4 October 2023)

New Features & Enhancements

• roles, a new member of the org struct that supports multiple roles per org ID per user, has been added to the /auth/me endpoint of the openapi spec. The roles struct member replaces the top level roles field, which has been deprecated.

Resolved Issues

• Previously, when an enterprise console user attempted to download the shipments.csv file after sorting some of the Shipments table columns, the following error message appeared: “Unable to download refund csv, please try again later.” This has been fixed so that users can successfully download the shipments.csv file no matter which columns have been sorted.

• Previously, the error message displayed during a failed attempt to download the shipments.csv file mentioned the refunds.csv file instead of the shipments.csv file. This has been fixed.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.4.2 (3 October 2023)

New Features & Enhancements

• The file size of the animated YubiKey on the YED Console login screen has been reduced.

Resolved Issues

• The IDP note on the Configure SAML Single Sign-On page under Settings in the YED Console has been updated to the following statement: “Note that each IDP has different labels for these fields, and the sequence of fields varies from one IDP to the next.”

• The YED console login page was struggling to load due to the file size of the page’s animated YubiKey. This has been fixed so the login page loads as expected.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.4.1 (28 September 2023)

Resolved Issues

• Previously, if a user toggled the Only show shippable inventory switch on the customer dashboard, but the customer did not have any remaining shippable inventory, the toggle and the inventory section of the dashboard disappeared. This has been fixed so the inventory section and toggle remain visible, and a message indicating “No shippable inventory found” is displayed.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.4.0 (28 September 2023)

New Features & Enhancements

• 1-Tier and 2-Tier Sales: YubiEnterprise Console now supports inventory purchase and consumption for Yubico and its channel partners - Distributors and Resellers as well as End-customers.

• Console: The Terms & Conditions for use of YubiEnterprise Services/Delivery have been updated and with the release of version 2.4.0, all new and returning users will need to indicate acceptance, otherwise they will not be able to log in to the Console. Each user’s acceptance will be logged with the relevant timestamp.

• Console: Console Owners can now assign, add, view and remove the Distributor role as needed for efficient user management within the organization.

• Console: Console Owners can now assign, add, view and remove the Reseller role as needed for efficient user management within the organization.

• Console: Distributor view of Reseller list: so that distributors can efficiently manage and monitor the resellers associated with their distributing activities, the Console displays a list of their resellers. For more information, see Roles and Permissions.

• Console: Reseller view of End Customer list: so that resellers can efficiently manage and monitor the end-customers associated with their reselling activities, the Console displays a list of their end-customers. For more information, see Roles and Permissions.

• Console: Because a user can have multiple roles/views in the same organization, the Users page lists the ones that apply for each user.

• Console: Automatic Selection of Login Role: If the user logging in to the Console has multiple roles, the highest priority role is selected, with the top role being Org Owner, followed by Org Admin, Org Auditor, Distributor, Reseller in that order. The user then arrives at the appropriate landing page.

• Console: SSO: The release of YubiEnterprise Services 2.4.0 heralds support for SSO initiated both by the Service Provider (SP-initiated SSO) and by the Identity Provider (IDP-initiated SSO).

• Console: IDP-initiated SSO: Org owners can now enable IDP-initiated SSO by logging in to the Console with credentials, going to the Settings > SSO tab, configuring IDP-initiated SSO, and clicking the new checkbox for it. For more information, see Supported SSO Initiation Forms.

• Console: SSO: Org owners logged in to the Console via SSO are now able to see whether IDP-initiated SSO has been enabled and view the URL for IDP-initiated SSO by going to the Settings > SSO tab.

• Console: All users are able to see on the Purchase Orders page the YE Delivery column showing whether the PO in question is available for shipping via YubiEnterprise Delivery.

• Console: The Shipment Creation page displays new information on the number of items available to be delivered: subscription products plus helper text for standard products.

• Console: On the Dashboard, there is no Create Shipment Request button if there are no products available for delivery.

• In the refunds.csv file, the channelpartner_name column has been renamed reseller_name and the channelpartner_id column has been renamed reseller_id. The values in the columns continue to be those for the channel partner name and ID.

• In the shipments download file (shipments.csv) the channelpartner_name column has been renamed reseller_name, and the channelpartner_id column has been renamed reseller_id. The expected values in these columns remain unchanged, i.e., the channel partner name and the channel partner ID.

• In the bulk_shipment_template.csv file that is downloaded when preparing to submit shipment requests in bulk, the ChannelPartnerID column has been renamed ResellerID. The expected values for this column remain the same.

Resolved Issues

• Console: New and returning customers are now asked to read and agree to the updated YubiEnterprise Console Acceptable Use Policy. Once the policy has been agreed to, the customer may access the console.

• Console: In the Shipments table, the tracking number was occasionally missing even though the status showed that the shipment had been delivered; however, the detail view of such a shipment would show the tracking number. This issue has now been resolved; the tracking number always shows up on the main page as well.

Known Issues

• If a user toggles the Only show shippable inventory switch on the customer dashboard, but the customer does not have any remaining shippable inventory, the toggle and the inventory section of the dashboard disappear. Workaround: reload the page or navigate away from the page and return to it.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

• Google Workspace cannot support both the Service Provider-initiated ACS URL and the Identity Provider-initated ACS URL at the same time. Neither is it possible to set up two different SAML Apps in the same Google Workspace, because Google Workspace enforces SP EntityID uniqueness across all SAML Apps in the workspace. For more information, see the Known Limitations section of the SSO topic.

Release 2.3.0 (31 August 2023)

New Features & Enhancements

• Console: Typically the shipment carrier needs the recipient’s telephone number for delivery. The Contact phone field for single shipments now has a tooltip explaining its purpose and the consequences of omission. “This phone number will be used by the carrier to complete the last stage of delivery. Submitting an invalid phone number may result in the order being returned to sender.” See Entering Shipping Information for context.

Known Issues

• Console: If you are on the second page of viewing a table (showing, for example, items 101-200) and you reload your browser, that second page you were on now displays as page 1 and the items that were 101-200 now display as items 1-100. The first page of the table has thus become inaccessible. Workaround: Change the size of the page.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.2.0 (27 July 2023)

Resolved Issues

• Console: The Dashboard was incorrectly counting some (but not all) refunded keys as remaining inventory. This issue has now been fixed, so that no refunded keys are counted as remaining inventory.

• Console: When using filters on the Shipments tab or the Purchase Orders tab, the operators that offered an alternative to “contains” used to spring back to the default, which is “equals”. This behavior has now been fixed, so that it is now possible to use the “contains” operator for Country code, Recipient, and Recipient email.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.1.4 (11 July 2023)

Resolved Issues

• API When creating a shipment request using the API, if the delivery_type (normal or expedited) was not given, the API was not applying the default (normal) to the request as expected. For countries to which only a single key at a time can be shipped and where only the normal delivery type is supported, shipment creation was therefore failing. This issue has now been fixed.

Known Issues

• Console: The Dashboard is incorrectly counting some (but not all) refunded keys as remaining inventory.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.1.2 (29 June 2023)

Resolved Issues

• API: Usage of the validate-address API for addresses in the following locations was failing with an undeliverable 400 response. Orders entered directly into the system and validated as part of the usual order processing were unaffected. This issue has now been resolved.
  • Australia
  • Japan
  • New Zealand
  • Indonesia
  • Philippines
  • Singapore
  • Thailand
  • India
  • Mexico
  • Chile

• Console: When filters were used, there was a problem clearing (resetting) the filter when no search results were found. For example, if advanced search was used on the Shipments tab or the Purchase Orders tab, and the search term yielded no results, the search term in the filter could not be changed - unless the browser window was reduced before clicking CLEAR ALL again. This issue has now been resolved; it is no longer necessary to shrink the browser window in order to change the search term.

Known Issues

• Console: The Dashboard is incorrectly counting some (but not all) refunded keys as remaining inventory.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.1.0 (22 June 2023)

New Features & Enhancements

• Single Sign-on (SSO) for Google Workspace: YubiEnterprise Console now supports SSO for Google Workspace. For further information and instructions, see Enabling SSO with Google Workspace.

• Self-enablement for Single Sign-On (SSO): Using the Console, Console Owners can now enable SSO for a variety of Identity Providers (IDPs). For more information, see Enabling SSO for Other IDPs.

• Improved Console Navigation: To improve user experience and flow for upcoming features, the horizontal navigation menu is now a left sidebar.

Resolved Issues

• The orgId field in the response to the following APIs was deprecated by the OpenAPI specs. The following APIs no longer return values for that field. Therefore it is advisable not to write more code that depends on the orgId field:
  • GET v1/inventory
  • GET v1/inventory/channelpartners/{channelpartnerId}
  • GET v1/purchaseorders
  • GET v1/purchaseorders/{purchaseorderId}
  • GET/POST v1/shipments
  • GET/PUT v1/shipments/{shipmentId}
  • GET/POST v1/shipments_exact
  • GET/PUT v1/shipments_exact/{shipmentId}
  • GET v1/accountbalances

Known Issues

• Console: The Dashboard is incorrectly counting some (but not all) refunded keys as remaining inventory.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.0.4 (5 June 2023)

Known Issues

• Console: The Dashboard is incorrectly counting some (but not all) refunded keys as remaining inventory.

• The orgId field in the response to the following APIs has been deprecated by the OpenAPI specs. Although these APIs currently return values for that field, future versions of the API will not return the orgID field. Therefore it is advisable not to write more code that depends on that field:
  • GET v1/inventory
  • GET v1/inventory/channelpartners/{channelpartnerId}
  • GET v1/purchaseorders
  • GET v1/purchaseorders/{purchaseorderId}
  • GET/POST v1/shipments
  • GET/PUT v1/shipments/{shipmentId}
  • GET/POST v1/shipments_exact
  • GET/PUT v1/shipments_exact/{shipmentId}
  • GET v1/accountbalances

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.0.3 (2 June 2023)

Resolved Issues

Console: Individual shipment request: Even though the Region/State line of the address had actually been entered and the shipment request submitted, that line was shown as empty in the shipment request record. Updating the request did not resolve the issue; the field remained blank. This issue has now been resolved and the data entered in the Region/State line of the address is now displayed in the record of the submitted request.

Known Issues

• The orgId field in the response to the following APIs has been deprecated by the OpenAPI specs. Although these APIs currently return values for that field, future versions of the API will not return the orgID field. Therefore it is advisable not to write more code that depends on that field:
  • GET v1/inventory
  • GET v1/inventory/channelpartners/{channelpartnerId}
  • GET v1/purchaseorders
  • GET v1/purchaseorders/{purchaseorderId}
  • GET/POST v1/shipments
  • GET/PUT v1/shipments/{shipmentId}
  • GET/POST v1/shipments_exact
  • GET/PUT v1/shipments_exact/{shipmentId}
  • GET v1/accountbalances

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 2.0.0 (25 May 2023)

New Features & Enhancements

• Console Subscription Management: The dashboard view has been upgraded to enable a better overview of the different subscription plans/tiers within the primary, backup and replacement categories, along with the licenses available as a portion of the total licenses. In addition, the supported form factors are shown for each plan/tier/category. Not only does this improved user interface facilitate subscription management, but it also makes ordering product shipment easier in that the request can be started directly from the inventory display. For more information including screenshots and explanations, see Dashboard.

• Enhanced Search The search function on the Shipments tab and the Purchase orders tab in the YubiEnterprise Console has been enhanced to enable advanced search. All the columns can be displayed and/or hidden; the Filters enable use of “Contains” or “Equals” operators; and the Density option enables setting the display view to compact, standard or comfortable. For more information, see Modifying the Table View for the Shipments tab and Modifying the Table View for the Purchase orders tab.

• Sub-processors: We are pleased to notify users that we have published a sub-processor webpage located here which lists sub-processors used on Yubico’s behalf as part of Yubico’s product and service offerings. To stay up-to-date on Yubico sub-processors, users can subscribe to an RSS feed or check the webpage for updates.

Resolved Issues

• The API endpoints GET /v1/inventory and GET /v1/inventory/:channelpartnerId no longer return a response that includes the field product_tier. The API is therefore now in conformity with the documented behavior.

Known Issues

• The orgId field in the response to the following APIs has been deprecated by the OpenAPI specs. Although these APIs currently return values for that field, future versions of the API will not return the orgID field. Therefore it is advisable not to write more code that depends on that field:
  • GET v1/inventory
  • GET v1/inventory/channelpartners/{channelpartnerId}
  • GET v1/purchaseorders
  • GET v1/purchaseorders/{purchaseorderId}
  • GET/POST v1/shipments
  • GET/PUT v1/shipments/{shipmentId}
  • GET/POST v1/shipments_exact
  • GET/PUT v1/shipments_exact/{shipmentId}
  • GET v1/accountbalances

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.33.0 (20 April 2023)

New Features & Enhancements

• Console: Shipment Recipient name OR Recipient company name: a new tooltip clarifies requirements for these fields: “At minimum, either a recipient first name and last name is required OR a recipient company name. When sending to a residential address, provide a first and last name but not a company name (can cause delivery issues). A company name should only be provided when sending to a commercial/business address.” This means that for business (corporate) addresses, both recipient name and company name can be provided, whereas for residential addresses, the company name must be left blank.

Resolved Issues

• Login When a WebAuthn credential nickname has more than 255 characters, a 500 error would be returned. This validation issue has now been fixed, so that the SQL exception that occurs when attempting to write the new name to the database now returns a 400.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.32.0 (23 March 2023)

New Features & Enhancements

• SSO: YubiEnterprise Services now supports Single Sign-On (SSO). For details, see Single Sign-On (SSO).

• System Email Upgraded to UTF-8 in order to support many languages and more email clients.

• Additional YubiKey Models
  • The YubiKey 5C NFC is available in Advanced, Premium, and FIPS tiers.
  • The Security Key C NFC by Yubico is available in Base, Advanced, Premium and FIPS tiers.

• Demo Password Reset: Console Owners can now reset passwords for Demo users. Those users follow the reset link from the email the system sends them and register passwords. They are not required to have YubiKeys in order to authenticate.

Resolved Issues

• Expedited shipping is not supported for certain countries. Those countries are listed in Key Quantities and Delivery Types. It is therefore no longer possible to select this option when shipping to those countries.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.31.0 (16 February 2023)

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.30.2 (24 January 2023)

New Features & Enhancements

• New Products: As of the current release, 1.30.2 on 24 January 2023, YubiEnterprise Services offers the following new products:
  • Security Key NFC by Yubico
  • Security Key C NFC by Yubico
  • Security Key NFC by Yubico - Enterprise Edition
  • Security Key C NFC by Yubico - Enterprise Edition

Subscription (2.0)

• Subscription (2.0): YubiEnterprise Services is launching Subscription (2.0) with this release 1.30.2 on 24 January 2023. Available for 500 users or more, it provides:

  • Procurement that is fast, predictable, and cost-effective
  • The opportunity upgrade to higher tiers as needs evolve
  • Form factor flexibility
  • The option to purchase backup YubiKey subscriptions at a discount to ensure your backup authentication mechanism is as strong as your primary one and to enable easy self-service account recovery.
  • 24x7x365 Priority Technical Support, which offers easy access to Yubico security experts (Yubico Support Services Overview)
  • Extended warranty: Warranties cover the initial term of the subscription plus the first renewal - the duration of the subscription.

  Plus Plan

  • Replacement licenses allow you to cover up to 25% of subscribed users per year, with an option to add on additional users as needed a la carte, due to turnover, lost or stolen keys, and upgrades.
  • Maximum discount on backup licenses
  • 5% of base purchase as funds available to apply toward Professional Services
  • Option for one bulk customization event per year included.

  Standard Plan

  • Choose the number of replacement licenses for turnover, lost or stolen keys, and upgrades.

Known Limitations

• Inventory/From Stock: Although Console users can specify the inventory they want to draw from, this option is not available when using the CSV file with the API or when creating bulk shipments. These latter two methods only permit specifying the kind of stock (initial, replacement, buffer). When inventory is not specified or cannot be specified, the system uses the “first in, first out” rule, which means it will deduct from the oldest PO first.

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.30.0 (19 January 2023)

Resolved Issues

• Console When a user and/or a password was reset, there was no indication whether the action had been successful. This issue has now been fixed: now a message confirming success is displayed after a user and/or a password is reset.

• Console: When you created a custom email and your HTML code was validated, the display of your actual code was stuck on the far right of the frame. This issue occurred whether the code had errors or not, and whether or not it exceeded the 65,000-character limit. This issue has now been fixed, and your HTML code is readable as expected, distributed evenly across the whole area of the frame.

• Console The Advanced Search by address did not work as expected unless you had street lines 2 and 3 in the address. The workaround was to add a space after each potential line of the address, including lines whose potential was unrealized, i.e., unoccupied fields. Therefore, when you were searching on an address that did not have a street line 2 or 3 you would have needed to add three spaces between street_line1 and city. This issue has now been fixed.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.29.2 (22 December 2022)

Resolved Issues

• The refunds CSV download button now works as expected.

Known Issues

• The .csv file created when downloading processed refunds is showing the wrong data in the inventory_product_type column. Instead of showing information such as “Standard Products”, “Shipping”, or “Primary Subscr - Adv. Tier: Initial, it is showing the name of the product that was refunded (e.g. YubiKey 5 NFC) or in the case of Shipping, it it is showing and empty field.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.29.0 (15 December 2022)

New Features & Enhancements

• Console and API Shipments initiated without using YubiEnterprise Services are now tracked within the Console and via the API. In order to distinguish between requests shipped using YubiEnterprise and those shipped without, we have introduced two types of shipment: “Automated,” which are those requested using YubiEnterprise Delivery, and “Manual,” which are shipments requested directly from Yubico or a Channel Partner. Therefore the table on the Shipments tab and the CSV download both now have a new column, “Type,” upon which one can filter. For more information, see Shipment Requests.

Resolved Issues

• Console and API The limit for the number of alphanumeric characters in the recipient email address, formerly 40, has been expanded to 80 characters. For more information, see the Shipment Request Fields table.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.28.0 (17 November 2022)

New Features & Enhancements

• Console: A search produces a filtered list of shipments. Until now, when you investigated one of those results and then clicked the Go back button, the results of that search were no longer available. With the current release, YubiEnterprise Delivery 1.28.0, the list of search results is retained even after clicking into a particular result or refreshing the browser window while on a page of search results. (For more details, see Searching Shipments.)

• Console: Customization of the SHIPPED/DELIVERED/DELIVERY EXCEPTION email template - An owner or an admin can edit the templates for these emails notifying a YubiKey recipient about a shipment. The HTML code for the new template is validated as the content is entered. When the user clicks Update the Send sample button becomes active so that the user can send themselves a sample email from the customized template. For more details, see Customizing Automated Emails.

• Console: When creating a new shipment, the single shipment tab is shown by default instead of the bulk shipment tab.

Resolved Issues

• Console: When logging into YubiEnterprise Delivery with the wrong email or password, the error message in the past was “Access denied.” Now the error message is “Incorrect email or password.”

• The status of some of the GB-destined shipments carried by Royal Mail was not updating promptly. Expected behavior is for the status to be shown as “Delivered” when that is the case; instead the status of shipments that had already been delivered was sometimes shown as “Shipped:In Transit”. This issue has now been fixed.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.27.3 (28 October 2022)

Resolved Issues

• There was a brief period of time in which the tracking numbers in the links for Blue Dart’s India shipments pointed at nonexistent shipments. Those tracking numbers have been corrected, so the links now point to the appropriate shipments.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.27.0 (20 October 2022)

Enhancements

• The advanced search feature for shipments has been substantially enhanced (see Searching Shipments).

Resolved Issues

• Prior to release 1.27.0, API calls that included saving an excessively long string to the street_line3 field such as the POST /v1/shipments_exact API received a peculiar error. Trying to save a string longer than 60 alpha-numeric characters now throws a better error.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.26.1 (26 September 2022)

Resolved Issues

• Previously, if the last remaining user of an org attempted to remove themselves from that org, they were automatically logged out of the console. This has been fixed so that users attempting this operation (which is not allowed and will result in an error message) remain logged in.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.26.0 (22 September 2022)

New Features & Enhancements

• Whitespace is now trimmed from the following fields in the bulk order request CSV file:

  • channel partner ID
  • inventory type
  • delivery type
  • key quantities

  Trimming will help prevent the CSV file parser from falsely rejecting these fields.

• When a user attempts to change their account password, and the new password violates any of the password requirements, an error message in red containing the first violated rule will appear on screen.

• The items in the top navigation bar (Dashboard, Shipments, Purchase orders, Settings) are now clickable from within a subpage of a particular item/tab. For example, a user can now click on Shipments from within a shipment detail page to navigate back to the main Shipments screen.

Resolved Issues

• The “Inactive” user status has been renamed as “Deactivated.”

• The unused /organization/update-setting API endpoint has been removed.

• Previously, when a console user navigated to the Users tab under Settings and reduced the number of users shown per page to 5, the delete (trash can) icon for the 4th user disappeared. This has been fixed so that the delete icon is available for all users shown on screen.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.25.2 (24 August 2022)

New Features & Enhancements

• API Token: Notification of token expiry is now emailed not only to the token holder but also to the org owner. (For more information on this, see Generating API Tokens.)

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.25.0 (18 August 2022)

Resolved Issues

• CSV: If the country code column in the CSV upload file had a space inserted in the country code, for example, a trailing space after “US” so that the system read it as “US “, upload of the CSV file would fail without an error. This issue has now been fixed.

• With shipments to the UK, in rare cases a shipment’s status was not progressing beyond Shipped: In Transit, although the carrier’s website was showing a delivery exception notice. Without a status update, no delivery exception email could be sent to the shipment recipient. This issue has now been resolved.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.24.0 (21 July 2022)

New Features & Enhancements

• Shipments destined for the US or Canada have been standardized to use the USPS codes for state or province. Every shipment request method now uses this input: individual shipment requests made via the Console or the API and bulk requests using the CSV file all require the USPS codes. The mappings between full names and codes are given in USPS Region/State Codes. As of the current release, use of these USPS codes is mandatory. Shipment requests that do not adhere to this standard will generate an error message, and no shipment will be created.

Resolved Issues

• Console: In the table on the Shipments tab, shipments were not sorting correctly on the ship_date or the delivery_date columns. Shipment requests should have been sorted into chronological order based on the selected column. Now the sequencing of requests in these columns is displayed correctly in chronological order when the sort icon for either of these columns is clicked.

• Some shipments sent to India have a status of “Delivered,” even though the carrier and tracking number are still showing as “coming soon.”

• Some shipments sent through India Post and delivered by the Transnet carrier made no progress through the expected statuses; they remained in the Shipped:In Transit state even after the shipment was delivered. This issue has now been fixed; all India Post shipments sent via Transnet are now tracked and therefore make the expected progress through the statuses.

Known Issues

• CSV: If the country code column in the CSV upload file has a space inserted in the country code, for example, a trailing space after “US” so that the system reads it as “US “, upload of the CSV file will fail without an error.

Known Limitations

• CSV: The CSV bulk upload does not support combining subscription and non-subscription products in a single shipment. Workaround: Use the API or the Console (from the Dashboard or the Shipments tab, Create shipment request > Single shipment) to create single shipment request that includes both types of products.

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.23.0 (23 June 2022)

New Features & Enhancements

• Shipments destined for the US or Canada can use the USPS codes for state or province. Every shipment request method has been standardized for this input: individual shipment requests made via the Console or the API and bulk requests using the CSV file all take the USPS codes. The mappings between full names and codes are given in USPS Region/State Codes. As of YubiEnterprise Delivery release 1.24.0 scheduled for 21 July 2022, use of these USPS codes will be mandatory. After this date, shipment requests that do not adhere to this standard will generate an error message, and no shipment will be created.

• Console Each Purchase Order now has its own detail page, showing PO number, whether direct or channel sale, and if the latter, the seller’s name, the expiring date for initial or perpetual stock, address and contact information. The available inventory is shown as before.

Known Limitations

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• India shipments: Some of our shipments to India use India Post for the last mile. India Post does not support our automated shipment tracking service, and therefore the tracking ID that YubiEnterprise Delivery displays is not actually a link. Workaround: Copy the India Post tracking number (typically 13 digits starting with E, R, or C) and paste it into either the India Post website - https://www.indiapost.gov.in/_layouts/15/dop.portal.tracking/trackconsignment.aspx (“Evaluate the expression” means do the arithmetic displayed in the box to prove that you are not a bot) or any of the other tracking service sites that support India Post, such as Ship24.com - (https://www.ship24.com/couriers/india-post-tracking).

Release 1.22.1 (25 May 2022)

Resolved Issues

• For shipments sent to India, status emails declaring that the shipment had been sent were being generated every hour. This issue has now been fixed.

Known Limitations

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see :ref:channel-partners-label.

Release 1.22.0 (20 May 2022)

New Features & Enhancements

• With the release of version 1.22.0, the tracking of shipments to India becomes more transparent. On the Console, clickable tracking numbers are now provided for shipments delivered by Blue Dart, one of our main carriers on the Indian subcontinent. The API too returns a tracking_link value.

Resolved Issues

• Shipments sent to GB/UK now transition relatively quickly to “Delivered” or “Delivery Exception” instead of remaining in the “Shipped: In Transit” status indefinitely.

• Console: The Purchase Order sorting function did not work. Clicking on a column heading did not result in the content of the column being sorted. This issue has now been fixed, and any column can now be sorted as expected.

Known Limitations

• For European shipments using Bpost, also known as the Belgium Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and paste it into the field for that purpose on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or into Parcelsapp.com’s page for Bpost tracking, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see :ref:channel-partners-label.

Release 1.21.0 (26 April 2022)

Resolved Issues

• If a field has been selected for sorting on any of the console list screens, that field title will now be shown in bold.

• Email addresses are now validated during shipment request creation for single and bulk shipments.

• The channel partner name field in the shipments .csv file is now populated for all entries, including direct sale shipments.

• Previously, when an order received a Delivery Exception status, an internal message was shown in the console. This has been fixed so the message is no longer shown.

• The API documentation has been updated to reflect that the suggested address fields (suggest_street_line1, suggest_street_line2, suggest_street_line3, suggest_city, suggest_region, and suggest_postal_code) are largely deprecated and will return an empty string. This applies to the following APIs: GET /shipments_exact, POST /shipments_exact, GET /shipments_exact{shipmentId}, and POST /shipments_exact{shipmentId}.

• The suggest_recipient field of the API, which is never returned in responses, has been removed from the API.

• On the Users screen under Settings, the alphabetic sort was not working properly when trying to sort users by email address. The sort function has been fixed and now behaves as expected.

• Role and State are no longer sortable fields on the Users screen under Settings in the console.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

Release 1.20.0 (24 March 2022)

New Features & Enhancements

• Console/CSV/API: Consistency in the requirement for recipient telephone number in shipment requests is now system-wide. When creating a single shipment request in the Console (i.e., using the GUI), phone number has always been a required field. Now bulk shipment requests via CSV upload also require phone number, as do shipment requests made via API. With the current release of YubiEnterprise Delivery - 1.20.0 - shipment requests that do not include recipient telephone number (“Contact phone”) will no longer be processed. Although the /shipments API is deprecated, this requirement will be enforced on that API too.

• Console/CSV/API Shipment request statuses will now be updated to reflect changes reported after requests have reached the “Delivery Exception” state.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

Release 1.19.0 (24 February 2022)

New Features & Enhancements

• Console: The detail view of the shipment request now displays Total cost and Product cost in the Shipping and tax section of the page instead of at the top, where it was previously shown.

Resolved Issues

• The POST validate-address API that is used to determine whether an address is acceptable by YED for delivery contradicted the POST shipments_exact API in that the first deemed an address without a city acceptable, while the second deemed it unacceptable, since city is a required field. The validate-address API has now been fixed; it too requires the city field and its rules are consistent with the rules of the POST shipments_exact API.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

Release 1.18.0 (20 January 2022)

New Features & Enhancements

• API Holders of API tokens are notified before expiry of a token via an automatically generated email sent to the address associated with the token. The email is sent 7 days before expiry, the day before expiry, and on the day of expiry.

Resolved Issues

• When the CSV file containing shipment requests was generated, the inventory_type column was not always populated for every row in the file. This issue has now been fixed.

• In the email that the system sends to notify recipients that a shipment will arrive, the carrier field was not consistently populated, nor was the link added to the carrier’s tracking number. This issue has now been fixed, and both the carrier and the tracking link are included in the email. API: This also resolves the issue of the incomplete response that was returned for the shipment order in the GET /shipments_exact and GET /shipments_exact/<shipmentId> responses: they now return comprehensive information.

• In the user guide, the section entitled Using the API to Execute a Shipping Request had a typo in the second sentence, which prevented the following information from being displayed at that location. “Although the system can deliver to Post Office (PO) Boxes within the United States, delivery to PO Boxes (or the equivalent) elsewhere in the world is unlikely to succeed.” This has now been fixed, so that the information now appears in this location.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

• API When getting a purchase order by its ID, extra, undocumented fields are returned. When a GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes is_vat_valid, is_tax_exempt, is_post_pay.

Release 1.17.2 (10 December 2021)

Enhancements

• Fifteen more countries have been added to the list of deliverable shipment destinations. The lists of countries and the corresponding limitations are given in Key Quantities and Delivery Types.

Resolved Issues

• Console: Shipments to overseas PO boxes (non-USA) are not delivered; instead, they are returned by all carriers. The Console now displays a warning to this effect when a shipment request is created using an overseas PO box. This limitation is referenced in Post Office Box as Destination.

Release 1.17.0 (18 November 2021)

New Features & Enhancements

• Console: Owners, Admins, and Auditors can now view the list of refunds for lost or missing shipments, drill down into the details of each item, and download a CSV file containing this data. For more information, see Viewing Processed Refunds.

Resolved Issues

• Console: Including leading or following whitespace with a term entered in the Search field yielded no results, even if the search term ought to have produced results. This issue has now been resolved; the system automatically trims any whitespace of this kind before the search is performed.

• When a shipment request was made providing a company name as recipient, plus either recipient first name or recipient last name, a validation error was returned. This issue has now been resolved: no error is thrown when the company name plus either first name or last name is provided.

• Console: The edit icon on the shipments page redirected the user to the shipment details page instead of showing the edit view in the same page. This issue has now been resolved, and it is now possible to edit in the same view.

• The status summary for shipments that were cancelled indicated that the shipments had been delivered, even though they were not. This issue has now been fixed: the status summary correctly shows canceled shipments as such.

• API integrations: The API documentation for the GET /shipments_exact API (to get all shipments) erroneously said that all the items included in the shipment (shipment_items) would be returned; that was incorrect - the field (shipment_items) was not returned in the response. This is no longer the case, and the API documentation now accurately reflects that the shipment_items field is not returned in the response.

• Console: After login, the Dashboard did not show any data. Only when the page was refreshed or one was redirected back from another page did the page load and show relevant data. This issue has now been resolved: the Dashboard page loads upon login and displays all data.

Known Issues

• API When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

• When the CSV file containing shipment requests is generated, the inventory_type column is not always populated for every row in the file.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner,

Release 1.16.0 (21 October 2021)

New Features & Enhancements

• Eight new countries are available for existing and new organizations to ship to. They are: India, Saudi Arabia, the United Arab Emirates, Mexico, Chile, Israel, Taiwan, and Hong Kong.

• Fulfillment partner [“Provider”] information is now displayed:
  • On the Console, on the shipment details page, in the Shipping & tax section
  • In the API, in the carrier field.

• API PUT /shipments/makedraft has been deprecated and is therefore no longer available.

Known Issues

• API: When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.15.0 (23 September 2021)

New Features & Enhancements

• Seven new countries: It is now possible to have shipments sent to Australia, New Zealand, Japan, Singapore, the Philippines, Indonesia, and Thailand.

Resolved Issues

• In cases when particular carriers were used to ship an order, shipments were not progressing beyond the SentForFulfillment state. The system now handles additional carriers correctly.

• Very occasionally, shipments did not have their delivered_date set. This issue has now been resolved, and all shipments that reach their target recipient have a delivered_date.

• On the Purchase Order popup, the channel partner name and partner ID were not shown the same way as they were in the shipment popup. The presentation of this information has now been rationalized so that it appears with the same formatting and in the same detail in both locations.

• Disabled Update Button When a shipment request was in the Awaiting validation state, it was not possible for the creator of the request to edit any field other than the from stock/key counts field. Even though the user was able to click the Shipment id link to open the shipment details page, the Update button remained disabled by default. This issue has now been resolved: it is possible to update all fields on the shipment details page even when the request is in the Awaiting validation state.

• Insufficient inventory

  • To maintain the window during which orders can be updated, edited, or recalled/deleted, orders are held and processed in batch. Therefore there might be less inventory available by the time an order is processed than what was shown in purchase order details when the request was created. For example, the person starting to create a shipment request assumes that the 50 keys the console shows they have in inventory will still be available by the time the shipment request is submitted. When this is not the case, any shipment requests processed after the inventory is exhausted will be flagged Error: Processing Error, contact support.  Reason is Not enough Inventory for Shipment - ShipmentStateError.
  • A second issue arises from the same source: when the user clicks on the shipment request ID with that error, part of the status message displayed is “Insufficient Inventory of Product X” where “X” is an integer. To find out what X means, consult the Product Name, Stock/Inventory, product_id and inventory_product_id table.
  • A third issue arises from the same source: it is not possible to make single shipment requests for products that are not available in inventory - which is expected if insufficient product has been purchased, but an insufficiency of inventory can also be caused by Yubico itself running out of stock.

  Workaround: Either contact Support to get more inventory, or edit the request to switch to another product for which inventory is available.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.14.0 (19 August 2021)

New Features & Enhancements

• Shipment requests: The alphanumeric character limits on the Console fields and the cells in the CSV upload file and the API have been expanded. For exact details, see the table detailing these limits in Shipment Request Form Fields.

• The shipment request detail popup has been expanded to a full page in order to display more information.

Resolved Issues

• API: For POST validate-address, street_line1 limit is 60 alpha-numeric characters.

• The unit price of the products is shown on the Purchase Order popup if the products were purchased directly from Yubico (as opposed to from a channel partner).

• Single shipment request: The product list is now filtered by the partner selected. In other words, selecting a channel partner determines which products are available for shipment and the quantities thereof.

• Bulk shipment request: The CSV file’s ChannelPartnerId column requires that the ID be explicitly entered instead of defaulting to “1” for Yubico (direct sale). This facilitates the avoidance of errors.

Known Issues

• API When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.13.0 (22 July 2021)

New Features & Enhancements

• Channel Partners: This feature enables the inclusion of Yubico’s channel partners in YubiEnterprise Delivery. Customers can distinguish between inventory purchased directly from Yubico and inventory purchased through our channel partners. This information is displayed on the Purchase Order (PO) tab by clicking on the individual PO IDs (see Viewing PO Details). When requesting individual shipments using the Console, the channel partner is specified via the Channel Partner dropdown (see Shipping to a Single Address), while for bulk upload of shipment requests, the ChannelPartnerId column in the CSV file is must be populated see: Shipment Request Form Fields). This feature is fully described in Purchasing from Resellers in “Requesting Shipment” in this guide. The updated APIs are listed under a heading with the same name, Purchasing from Resellers, in the “API Onboarding Playbook” in this guide.

• The default Delivery Exception email no longer references and links to Yubico’s support website. This enables enterprise customers to divert any support requests from shipment recipients (end users) to their own IT team.

• Download CSV: A new field, recipient_company, is now included in the exportable .csv file containing all shipment requests. This is the equivalent of the Company field in a single shipment request.

Resolved Issues

• API: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

• There was an issue where the user ID associated with a shipment request was being updated to the ID of the last user to edit the shipment. The requester ID is supposed to be the ID of the user who originated the request and should not change once the order is created. A side effect of this was that it was possible for the shipment to get into a state in which it was not viewable/editable/delete-able. The fix was to ensure that the requester ID always remains unchanged.

• API: Now suggest_postal_code returns the correct information. Previously, this was never correctly returned, which affected the following APIs:

  • GET /shipments_exact
  • GET /shipments_exact/{shipmentId}
  • PUT /shipments_exact/{shipmentId} because the response to that is the full shipment payload, which includes the suggest_postal_code field.

  It had no effect on the POST /validate-address API.

Known Issues

• When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, is_post_pay).

Known Limitations

• Channel Partners: To order keys via API from inventory purchased through channel partners, the new /shipments_exact APIs must be used. The older, deprecated /shipments API only supports ordering keys from inventory purchased directly from Yubico. For more information, see Purchasing from Resellers.

Release 1.12.0 (24 June 2021)

Resolved Issues

• Search function: when a search had 0 results, you could type any page number without an error being displayed. This issue has been resolved.

Known Issues

• When getting a purchase order by its ID, extra, undocumented fields are returned. When a request for GET /v1/purchaseorders/{purchaseorderId} is sent, the response includes (is_vat_valid, is_tax_exempt, and is_post_pay).

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.11.2 (26 May 2021)

Resolved Issues

• The status of shipment requests that had already been sent out for fulfillment was not updating as expected. The status of those orders remained stuck at “Processing: Queued for Fulfillment” instead of progressing to “Processing: Sent for Fulfillment”. This issue has now been resolved.

Known Issues

• Search function: when a search has 0 results, you can type any page number without an error being displayed.

• The .csv template for bulk shipment requests sometimes contains a column for a product that you do not have, e.g., the YubiKey 5 NFC might not be available to you and yet the template has a column for it. If you attempt to use this column, your bulk shipment request will be rejected for containing an invalid product ID.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. However, the delivery status does, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.11.0 (20 May 2021)

New Features & Enhancements

• API Token: timestamps for creation, last use, and expiry are now shown on the profile page for that user. This information is shown for all tokens used since YubiEnterprise Delivery release 1.10.

• Automated emails sent by the system to end-users upon shipment / delivery / delivery-exception are now fully customizable. Formerly an organization owner or admin could use the Console to customize a paragraph that was then inserted into the standard email template. Now the UI shows one field for the subject of the email and a second for the email body. The customization performed here will apply to all emails sent by the system for that organization.

• The ability to search shipments by recipient_email has now been enabled.

• The Shipped_date now appears on the Dashboard of the Console and on the Shipments tab, as well as in the .csv download file containing the shipment requests.

• The Delivered_date now appears on the Dashboard of the Console and on the Shipments tab, as well as in the .csv download file containing shipment requests. This field is searchable.

Resolved Issues

• CRLF characters (Carriage Return (ASCII 13, r) Line Feed (ASCII 10, n)) were allowed in the address fields of individual shipment requests made via the Console. This resulted in unexpected line breaks in the corresponding row of the download CSV file. Those characters are now stripped from the input, so the CSV file no longer shows those line breaks.

• Data contained in downloaded .csv files of shipment requests was problematic, in that it caused a lack of alignment. This issue has now been corrected.

• When the same item was ordered from different types of inventory, e.g., primary/backup subscription, advanced tier, initial/replacement/buffer, the total quantity of the item from all types of inventory did not always add up correctly. This issue has now been fixed.

• If you entered a product type or quantity that was not available or inactive in the system, the shipping request was rendered incomplete, and the status message used the numeric ID of the product instead of its name (e.g., “ProductId 3 not active in the system”). This issue has now been resolved, so that the actual name of the product is shown, e.g., “YubiKey 5C not active in the system”.

• If you canceled a bulk shipment request after having uploaded a .csv file, the previously selected file name was displayed next to the Choose file button. This issue has now been resolved.

• If you hovered over your profile icon on the Console, instead of your organization name in the tooltip, you would see its ID in the YubiEnterprise Delivery system. This issue has now been resolved, and so the actual name of your organization is displayed in the tooltip.

Known Issues

• Search function: when a search has 0 results, you can type any page number without an error being displayed.

• The .csv template for bulk shipment requests sometimes contains a column for a product that you do not have, e.g., the YubiKey 5 NFC might not be available to you and yet the template has a column for it. If you attempt to use this column, your bulk shipment request will be rejected for containing an invalid product ID.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. The delivery status does, however, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.10.0 (22 April 2021)

New Features & Enhancements

• The .csv file for bulk import has always been limited to 10MB, but now the system returns a clear error message along with the 400 response code when a user attempts to upload a file that is too large.

• User Account Management: The list of users on the Settings > Users tab now displays a user status column. This enables adherence to compliance procedures when reviewing which users have access to the system.

• Enhanced Security: Session login limits: YubiEnterprise Delivery users do not stay logged in indefinitely. They are automatically logged out after 24 hours.

Resolved Issues

• Console search widget: the page counter is now reset to 1 for each new search.

• Console search widget: It was not possible to enter a page number that would have contained no search results; in other words, if there were only 10 pages of search results, you could not enter 100. It is now possible to enter a page number that does not exist because there were not that many results, but an error message explaining this is now shown.

• The available inventory displayed on the Purchase Order popup is now sorted.

• Making an /auth/machine-token API request with an expired token used to fail with a 500 error. Now such a request correctly returns a 401.

• When a user created a new API token and then switched orgs, the view did not update - the new token still appeared under the other org, even though the active token reference did update correctly. This has now been fixed.

• The email address of the user who created a shipment request is now shown in the pop-up window displayed by clicking on the ID of the shipment request.

• Broken links in the documentation have now been fixed.

• Users in demo mode are no longer able to edit the email template informing new recipients that they will be receiving shipments from YubiEnterprise Delivery. This capability is reserved for org owners and admins whose accounts are fully enabled (i.e., no longer in demo mode).

Release 1.9.0 (18 March 2021)

The initial API documentation link on Swaggerhub (https://app.swaggerhub.com/apis/yubico/yubi-enterprise-delivery-public/v1-oas3) is no longer updated and has therefore between removed. Please refer to: https://console.yubico.com/apidocs/ for the latest API documentation.

Enhancements

• User input is validated in such a way that the user is able to confirm or change input as required before submitting shipment requests; for example:
  • Indications of the allowed input for any given field are provided
  • Character rules are now provided for each API
  • The verification results for uploaded CSV files are now provided
  • Error codes have been standardized.

• YubiEnterprise Delivery users can now give their security keys (nick)names so that a user with multiple keys can distinguish them from each other. The console displays the keys in the order in which they were registered.

• API: Validation error responses are now consistent across the APIs.

• API Security:
  • If your request body does not contain valid JSON, the system informs you that the JSON contents you presented could not be verified and were therefore discarded.
  • When a user with permissions to change user roles attempts to grant a disallowed privilege level, the requested role is checked against a list of available roles and the error displayed to the user says only “a match was not found for a valid role”.

• When selecting products during the creation of a shipment request, users can now see the entire range of custom product options available to their organization.

• Organization owners can now reset just users’ passwords in addition to the existing option of resetting users entirely.

Resolved Issues

• Telephone numbers entered in shipment requests are now validated. If a mistake is found, the user is given the opportunity to correct it before the request is processed.

• API: Submitting invalid values for the delivery_type or inventory_type fields now triggers INFO-level errors instead of 500s.

• API: A JSON unmarshall error resulting from a malformed payload for the /shipments POST CreateShipment API used to send ‘500 / “unknown error”’’. This type of error now sends ‘400 / “invalid payload”’’.

• When your login has expired, clicking on the Generate API token on the profile page does not work. This issue has now been fixed.

• API: The auditor role can delete API tokens as well as create them.

• Transaction rollbacks are now logged at INFO level instead of at WARNING level, which was too severe.

• When an attempt is made to delete a shipment request that does not exist, the error code returned is now 404 instead of 500, which erroneously indicated a server problem. This issue has now been fixed.

• API: When Organization Products are returned, the TotalCount is now set.

• API: When calling InviteUserToCurrentOrganization for a user already in an organization, an AlreadyExists response is now returned.

• API: GET /shipments was missing the advanced_search parameter. This is now present.

• The CSV download was timing out. This issue has now been resolved.

Known Limitations

• For European shipments using Bpost, also known as the Belgian Post Group, the tracking number is not hyperlinked. The delivery status does, however, update correctly. Workaround: To find out where a Bpost shipment is, copy the tracking number and input it on Bpost’s page for that purpose, http://www.bpost2.be/bpostinternational/track_trace/find.php?lng=en or that of their partner, https://parcelsapp.com/en/carriers/belgium-post.

Release 1.8.3 (9 March 2021)

Enhancements

• Support for Transport Layer Security (TLS) v1.0 and v1.1 has been removed; the earliest version YubiEnterprise Delivery now supports is TLS 1.2. This update to the cryptographic protocols renders network communication less vulnerable to attack.

Release 1.8.0 (18 February 2021)

Features & Enhancements

• Security Enhancement: YubiEnterprise Delivery 1.8.0 implements an infrastructure enhancement that requires all users to reset their passwords. All users will have received an email from Yubico announcing this one week prior to the 1.8.0 release. The email explains the procedure to be followed: click on the link in the email, which takes you to a page enabling you to update your password. If you do not update it within one week, contact your YubiEnterprise Delivery organization owner for an account reset. If you are an Org Owner, contact YubiEnterprise Support.

• Using the API and the Console (GUI) for single shipments, it is now possible to include products from different inventory types within the same shipment. For details, see Shipping to a Single Address.

• Advanced Search for API Advanced search capabilities have been introduced for API users. Fields with different names will be searched in an AND, while fields with the same name will be ORed.

Resolved Issues

• When browsers truncated redirection URLs, or users manually copy-pasted incomplete URLs, the missing OAuth authorize parameters caused the login backend to crash.

Known Issues

• When your login has expired, clicking on the Generate API token on the profile page does not work. Workaround: Log in to the Console again.

Release 1.7.0 (21 January 2021)

Features & Enhancements

• API: Advanced search Lists of shipment requests can be filtered by query parameters. We introduced /search-description on searchable resources to provide a description of the searchable fields.

• Timestamps for shipment requests and for orders being shipped are now provided with millisecond precision from the Console (the GUI) and via the API.

• API We now return “404 Not Found” response {"message":"Product Id <> could not be found"} for GET /products/{product id} on an invalid product ID, as per the API contract.

• The CSV file download containing shipment requests shows streamlined shipment status, including for shipments carried out before the 1.7.0 release. For details, see Column Headings in Download File.

• The tracking number for each shipment is now associated directly with the shipping date, just as the “Shipped - in transit” status is directly linked to the date of shipment.

Resolved Issues

• Organization names were not being displayed correctly. This issue has now been fixed.

• Some European shipments did not show the correct tracking number link. This issue has now been fixed.

• When selecting shipments for bulk deletion, the number of shipment requests listed as available for deletion may not have matched the number displayed directly underneath the Back to Shipments button (e.g., “1 - 11 of 32” and yet there would be only a single item shown in the list). The number of items listed in the table was correct, not the number shown on the upper right. This issue has now been fixed.

• When the API was used to create a shipment request against a subscription that did not include the product you wanted to ship, the shipment details page (the popup for the shipment ID) on the Console (the GUI) for that request would show that the “ghost product” request was made against Standard products inventory. This issue is now fixed.

• In the YubiEnterprise Console (the GUI), the limit on the number of characters in the “Company” field has been raised from 15 to 20, so it now matches the limits on that field in the bulk upload as a CSV file and the API.

• Shipment requests with shipment_state_id=104 (ShipmentStateDelivered) will always have is_delivered=TRUE.

• Upon completing a single shipment request using the YubiEnterprise Console (the GUI), the button for creating another shipping request did not appear to be functional. Its name is now properly displayed, and this secondary button changes from white to dark blue when you mouse over it.

• When using the Console (GUI) to create a single shipment request and selecting first Standard products from the From stock dropdown, entering a quantity for any product, then selecting another item from From stock, the quantity previously selected in conjunction with Standard products disappears from view. However, the number entered is still in the system; it shows up in the confirmation message when you click Create Shipment.

• API In the validate-address API, some fields in the response payload and the US Address Component did not match the LOB API. This issue is now fixed.

Release 1.6.0 (19 November 2020)

Features & Enhancements

• With the release of YubiEnterprise Delivery 1.6.0, customers have more granular control in determining the stock inventory from which products are shipped. Previously, the system would choose the stock from the oldest Purchase Order in the system to ensure that the customer’s stock did not expire before use.

  • Explicit selection is now available for single shipment requests (see Shipping to a Single Address).

  • Bulk shipment orders will continue to use the original method whereby the system chooses the stock. Bulk shipment ordering will convert to the exact choice method in a future release.

  • A new set of delivery APIs has been made available to support the exact choice method, the suite of /shipments_exact APIs. The original /shipments APIs are deprecated starting in this 1.6.0 release but they will continue to be available until at least May 2021. Customers are encouraged to use the /shipments_exact APIs for any new development and to update existing clients soon.

    Shipping Requests: Listing, Tracking, Searching, Status etc.

    Deprecated	Replacement
    GET /shipments	GET /shipments_exact
    POST /shipments	POST /shipments_exact
    GET /shipments/{shipmentId}	GET /shipments_exact/{shipmentId}
    PUT /shipments/{shipmentId}	PUT /shipments_exact/{shipmentId}
    DELETE /shipments/{shipmentId}	DELETE /shipments_exact/{shipmentId}
    /UpdateShipmentById	shipments_exact/{shipment_id}
    /organization/update-setting	None

• Before adding Backup subscriptions to new Purchase Orders (POs), existing POs should be exhausted.

• Download of CSV file with shipment requests has been accelerated.

• Expedited shipments in the US will no longer use USPS Priority (for 1-99 items) and UPS Ground (for 100-500 items) but instead will be using UPS Overnight for 1-500 products. The cost of shipping has been adjusted accordingly.

• A new version of the original /address-validation API checks addresses more closely to ensure acceptance by the system. The deprecated API is /address-validation and the new one is /validate-address. The deprecated API will continue to be available until at least May 2021. Users are encouraged to use the /validate-address API for any new development and to update existing clients soon.

• The online Help can now be accessed from the login screen; it is not necessary to log in to access Help.

• Better navigation: When reviewing Incompletes, a new Go Back to Shipments button facilitates acceleration of the workflow.

• The Dashboard view more accurately reflects modes of purchase and stock in inventory. The new sections are Standard products inventory, Non-subscription inventory, and Subscription inventory.

Resolved Issues

• It is now possible to create a single shipment request combining different types of stock/inventory, for example both a lanyard from the Standard products option and a key from the Primary Subscr. Advanced Tier - Init option in the From stock dropdown.

• The Search function for the online help (User Guide and Release Notes) has now been fixed.

• Purchase Order (PO) display: Inventory counts of zero on POs are no longer shown as just a forward slash, but instead as expected, for example “0/100 - YubiKey 5C”.

• The detail view of Purchase Orders with “ghost” inventory is now available. “Ghost” inventory was caused by Yubico adding a product to an Organization and then removing it.

Release 1.5.0 (22 October 2020)

Features

• It is now possible to delete multiple shipment requests simultaneously. This is useful when the system is unable to validate multiple addresses or when the wrong CSV file was uploaded by mistake.

• The CSV file upload now accepts alternative values for DeliveryType: instead of just 1 for Normal and 2 for Expedited, the words Normal and Expedited are now acceptable input. Integer parsing will be retained for backwards compatibility.

API

• GET  /inventory has been extended so that it always returns product_mapping.

Resolved Issues

• Outstanding error messages are now cleared between shipment updates.

• Products no longer in inventory cannot be selected from the New shipping request page in the Console for a single shipment request. In the API, /shippablekeys returns only products still in inventory for inventory_type = 1.

Known Issues

When selecting shipments for bulk deletion, the number of shipment requests listed as available for deletion may not match the number displayed directly underneath the Back to Shipments button (e.g., “1 - 11 of 32” and yet there is only a single item shown in the list). The number of items listed in the table is correct, not the number shown on the upper right.

Release 1.4.0 (24 September 2020)

Features

• Improved /products API endpoint behavior: GET /products returns the list of products that are both a) in inventory and b) shippable.

• The delivery exceptions email feature has been completed.

Resolved Issues

• Inventory type in shipment requests always displays correctly now.

• The product images for multiple subscription tiers concurrently displayed are now consistent.

Release 1.3.1 (10 September 2020)

Known Issue

• When requesting shipment for a YubiKey Lanyard, the Inventory Type must be set at type 1, YubiKey Shipment, even if you are a subscription customer. This means that if you want to send a person both a lanyard and a key from subscription stock, you must make two separate shipment requests. Set the other inventory types as follows:

  Product <> inventory type mapping

  Product or Inventory Name shown on Purchase Order	Value to use for inventory_type
  YubiKey Lanyard	1
  Security Key C NFC by Yubico (Black)	1
  Security Key C NFC by Yubico - Enterprise Edition	1
  Security Key NFC by Yubico (Black)	1
  Security Key NFC by Yubico - Enterprise Edition	1
  YubiKey 5 Nano	1
  YubiKey 5 Nano FIPS	1
  YubiKey 5 NFC	1
  YubiKey 5 NFC FIPS	1
  YubiKey 5C	1
  YubiKey 5C FIPS	1
  YubiKey 5C Nano	1
  YubiKey 5C Nano FIPS	1
  YubiKey 5C NFC	1
  YubiKey 5C NFC FIPS	1
  YubiKey 5Ci	1
  YubiKey 5Ci FIPS	1
  YubiKey Bio - FIDO Edition	1
  YubiKey C Bio - FIDO Edition	1
  Advanced - Plus - Backup	3
  Advanced - Plus - Backup - Replacement	5
  Advanced - Plus - Primary	3
  Advanced - Plus - Primary - Replacement	5
  Advanced - Standard - Backup	3
  Advanced - Standard - Backup - Replacement	5
  Advanced - Standard - Primary	3
  Advanced - Standard - Primary - Replacement	5
  Advanced/Bio - Plus - Backup	3
  Advanced/Bio - Plus - Backup - Replacement	5
  Advanced/Bio - Plus - Primary	3
  Advanced/Bio - Plus - Primary - Replacement	5
  Advanced/Bio - Standard - Backup	3
  Advanced/Bio - Standard - Backup - Replacement	5
  Advanced/Bio - Standard - Primary	3
  Advanced/Bio - Standard - Primary - Replacement	5
  Backup Subscr - Adv. Tier: Buffer	4
  Backup Subscr - Adv. Tier: Initial	3
  Backup Subscr - Adv. Tier: Replacement	5
  Backup Subscr - Base Tier: Buffer	4
  Backup Subscr - Base Tier: Initial	3
  Backup Subscr - Base Tier: Replacement	5
  Backup Subscr - FIPS Tier: Buffer	4
  Backup Subscr - FIPS Tier: Initial	3
  Backup Subscr - FIPS Tier: Replacement	5
  Backup Subscr - Prem. Tier: Buffer	4
  Backup Subscr - Prem. Tier: Initial	3
  Backup Subscr - Prem. Tier: Replacement	5
  Base - Plus - Backup	3
  Base - Plus - Backup - Replacement	5
  Base - Plus - Primary	3
  Base - Plus - Primary - Replacement	5
  Base - Standard - Backup	3
  Base - Standard - Backup - Replacement	5
  Base - Standard - Primary	3
  Base - Standard - Primary - Replacement	5
  Base/Bio - Plus - Backup	3
  Base/Bio - Plus - Backup - Replacement	5
  Base/Bio - Plus - Primary	3
  Base/Bio - Plus - Primary - Replacement	5
  Base/Bio - Standard - Backup	3
  Base/Bio - Standard - Backup - Replacement	5
  Base/Bio - Standard - Primary	3
  Base/Bio - Standard - Primary - Replacement	5
  Compliance - Plus - Backup	3
  Compliance - Plus - Backup - Replacement	5
  Compliance - Plus - Primary	3
  Compliance - Plus - Primary - Replacement	5
  Compliance - Standard - Backup	3
  Compliance - Standard - Backup - Replacement	5
  Compliance - Standard - Primary	3
  Compliance - Standard - Primary - Replacement	5
  Non-subscription - Advanced Tier	2
  Non-subscription - Base Tier	2
  Non-subscription - FIPS Tier	2
  Non-subscription - Premium Tier	2
  Primary Subscr - Adv. Tier: Buffer	4
  Primary Subscr - Adv. Tier: Initial	3
  Primary Subscr - Adv. Tier: Replacement	5
  Primary Subscr - Base Tier: Buffer	4
  Primary Subscr - Base Tier: Initial	3
  Primary Subscr - Base Tier: Replacement	5
  Primary Subscr - FIPS Tier: Buffer	4
  Primary Subscr - FIPS Tier: Initial	3
  Primary Subscr - FIPS Tier: Replacement	5
  Primary Subscr - Prem. Tier: Buffer	4
  Primary Subscr - Prem. Tier: Initial	3
  Primary Subscr - Prem. Tier: Replacement	5

  • Use Inventory Type 1 if you have purchased keys on the perpetual mode and/or for lanyards.
  • Use Inventory Type 2, YubiKey Tier SKU Shipment, if you are not a subscription customer, but have purchased tiers of keys instead of physical keys.
  • Inventory Types 3, 4, and 5 are for subscription customers only.
    • Make sure to use up all of your Inventory Type 3, Initial, within the first year of your subscription.
    • Use Inventory Type 4 at any time: Buffer stock expires only at the end of your subscription term.
    • Use Inventory Type 5, Replacement, for users who have lost their keys or want to upgrade.

Release 1.3.0 (28 August 2020)

Features

• Enhanced and extended address validation status messages: error messages displayed as a result of failed address validation now give instructions for achieving successful validation.

• Improvements to the downloadable shipments CSV. It now shows for each shipment:
  • Organization name as well as org-ID
  • Purchase Order number
  • User email as well as user-ID
  • Delivery type indicating “normal” or “expedited”
  • Both shipment state ID and actual shipment state message
  • Both shipment product cost and shipment product taxes.

• Added YubiKey Lanyard to the product list.

• Begin preview of API to retrieve the available subscriptions.

Resolved Issues

• The customized email for DELIVERY EXCEPTIONS can now be sent as a preview sample to the logged-in YubiEnterprise Delivery user.

Release 1.2.0 (23 July 2020)

Features

• Updated Pricing
  • Introducing flat-fee shipping for up to 2 keys:
  • Introducing support for expedited shipping (1-3 days)

• Email customization and preview: The notification emails automatically sent to YubiKey recipients can be customized, and can also be previewed. Clicking the Send Sample button below the Customize Email field sends a sample of the customized email to the email ID logged into YubiEnterprise Delivery. For more details, see Notifying About Shipments.

• PREVIEW: Ability to download shipments table: Organization owners, admins, and auditors can download the information on the Shipments tab as a CSV file. There are two options:
  • The entire contents can be downloaded - i.e., all the rows in the table, even if there are multiple pages.
  • Search results. If a search term is entered into the Search field, the rows containing the search term will be downloaded as a CSV file.

• Subscription Shipping through YubiEnterprise Delivery: Subscription customers can view their inventory on the Dashboard, with:

  • Premium Tier Subscription
  • Premium Tier Subscription Replacement
  • Premium Tier Subscription Buffer.

  Subscription customers can specify shipment types:

  • Initial shipment
  • Buffer stock shipments
  • Replacement YubiKey shipment

  Subscription customers can download a CSV file with the contents of the shipments table (see “Ability to download shipments table” above), showing all the YubiKeys in the subscription tier and Subscription-Fulfillment-Type.

Known Issues

• The customized email for DELIVERY EXCEPTIONS cannot be sent as a preview sample to the logged-in YubiEnterprise Delivery user.

Release 1.0.0 (18 June 2020)

Features

YubiEnterprise Delivery enables organizations to manage orders of Yubico’s security keys (including YubiKeys), encompassing:

• Ordering shipment of a key or keys to a single address through the YubiEnterprise Delivery Console (the GUI) or the API
• Bulk upload of shipping orders for fulfillment using CSV files
• Shipping orders via the API
• Inventory management
• Tracking shipping costs
• Tracking shipment of the security keys you purchase from Yubico to the end-user
• Customizing auto-generated delivery notification emails
• Support for Virtual Product Tiers.

Known Limitations

• The following character limitations (including spaces) apply to all three methods of requesting shipment: Console (GUI), CSV, and API:
  • First Name: 15
  • Last Name: 20
  • Company: 20
  • Address lines 1, 2, 3: 40
  • City: 20

• In certain situations, if your computer has a platform FIDO authenticator such as Windows Hello and you want to enroll a YubiKey, the Windows UI displayed may ask you to enroll that other platform authenticator. Workaround: Hit Cancel to get to the YubiKey enrollment option.

Known Issue

• A shipment request whose status is indicated as ShipmentStateError must be recreated and resubmitted.

---

To file a support ticket for YubiEnterprise Delivery, click Support.