Release Notes

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 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

  • 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 channel-partners-label.

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 PO Detail View). When requesting individual shipments using the Console, the channel partner is specified via the Channel Partner dropdown (see Using the Console to Ship 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 Fields). This feature is fully described in Channel Partners in “Requesting Shipment” in this guide. The updated APIs are listed under a heading with the same name, channel-partners-label, 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

  • 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 channel-partners-label.

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

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

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

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

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.
  • 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 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 PO 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 Using the Console to Ship 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.

      Deprecated APIs and their Replacements
      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}
  • The full list of options potentially available is given below. The actual list depends on what you have purchased. Explanations for the terms in the list are given in the table below the list.

    With the release of YubiEnterprise Delivery 1.6.0, the distinction between Primary Subscription and Backup Subscription is made explicit, thus facilitating requesting shipment.

    Full List of Inventory Types

    • Primary Subscr - Base Tier: Initial
    • Primary Subscr - Base Tier: Buffer
    • Primary Subscr - Base Tier: Replacement
    • Primary Subscr - Adv. Tier: Initial
    • Primary Subscr - Adv. Tier: Buffer
    • Primary Subscr - Adv. Tier: Replacement
    • Primary Subscr - Prem. Tier: Initial
    • Primary Subscr - Prem. Tier: Buffer
    • Primary Subscr - Prem. Tier: Replacement
    • Primary Subscr - FIPS Tier: Initial
    • Primary Subscr - FIPS Tier: Buffer
    • Primary Subscr - FIPS Tier: Replacement
    • Backup Subscr - Base Tier: Initial
    • Backup Subscr - Base Tier: Buffer
    • Backup Subscr - Base Tier: Replacement
    • Backup Subscr - Adv. Tier: Initial
    • Backup Subscr - Adv. Tier: Buffer
    • Backup Subscr - Adv. Tier: Replacement
    • Backup Subscr - Prem. Tier: Initial
    • Backup Subscr - Prem. Tier: Buffer
    • Backup Subscr - Prem. Tier: Replacement
    • Backup Subscr - FIPS Tier: Initial
    • Backup Subscr - FIPS Tier: Buffer
    • Backup Subscr - FIPS Tier: Replacement
    • Non-subscription - Base Tier
    • Non-subscription - Advanced Tier
    • Non-subscription - Premium Tier
    • Non-subscription - FIPS Tier
    • Standard Products
    Standard Products Subscription Non-subscription
    Standard products are
    physical keys purchased
    outright (on your PO
    you will not find
    “Standard Products”,
    but instead the actual
    products/models that
    you purchased).



    There is a primary
    subscription and a backup
    subscription for each
    tier (product grouping):
    Base, Advanced, Premium,
    and FIPS. Each of those
    tiers has Initial,
    Buffer, and Replacement
    sub-categories, explained
    in the table below,
    The non-subscription
    tiers are for virtual
    keys. Unlike
    subscription tiers,
    non-subscription
    tiers have no
    sub-categories.




    Before adding Backup subscriptions to new 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.
  • 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 POs 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:

    Integer inventory_type (Stock) Purchase Mode
    1 YubiKey Shipment Outright purchase
    2 YubiKey Tier SKU Shipment Purchase of virtual keys
    3 Subscription - Initial Shipment Subscription
    4 Subscription - Buffer Stock Shipment Subscription
    5 Subscription - Replacement YubiKey Shipment Subscription
    • 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 End-Users of Shipment and Delivery.
  • 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.