Version 4 of the HP Authentication Suite of applications is due for release in October 2025.
Do not update firmware to V5.9.x
Search V4 Release update
Here is a List of Known issues and or limitations, you may also find the following link of some use. What's new
Reported October 2025
Urgent Notice - Please do not Upgrade firmware to 5.9.x, we have not certified HP Authentication suite with 5.9.x, We only support Firmware 5.8.x, and have noticed anomalies with 5.9.x
HP Authentication Manager V4
Limitation
You are Unable to register more than 15 User cards, Badges , QRCodes and or BLE ID's when using Self-Hosted Azure custom security attributes
Resolution
Your IT manager can remove unused Card ID's to allow for Maximum of 15 ID's
Best Practice for NFC/PCProx and BLE Reader Configuration
If you're using NFC/PCProx and/or BLE readers, it's best practice to ensure all devices are consistently programmed to output the same string length — such as 16-bit. Inconsistent configurations across readers can result in varying Card ID formats, which may lead to multiple identities being registered in Azure for the same physical credential (e.g., card, badge, or BLE token).
For example, if you have 30 card readers and each is programmed with a slightly different ID output length, a single user could end up with several distinct identities. This can cause sign-in issues, especially since Azure supports a maximum of 15 identities per user. To avoid authentication problems and ensure a smooth user experience, please standardize the output format across all card readers in your environment.
Please Review the following Article on how best to configure your Readers
Universal Print V4
Limitation
- Unable to display file size information for _Secure registered printers.
- Unable to display Date-Time & File size information for Print Anywhere Registered Printers
These limitations are within the IPP/Mopria standards which prevents the display of file size, date, and time details. These constraints are inherent to the protocol specifications and not a limitation of our application.
- Print jobs are deleted
If you preview a print job sent via Print Anywhere_Secure and choose not to proceed with printing, the job will be automatically deleted once you exit the preview screen. This behavior is a limitation of the IPP/Mopria standards and not a defect in the application.
We’ve requested Microsoft to investigate this issue further. However, please note that resolving it requires changes to the IPP Working Group and Mopria standards. These standards currently lack the necessary functionality to support our application.
Limitation
- No support for Finisher Options Fold-C, Fold-V, Fold Z, Fold Letter, Fold Half etc..
- Staples must be manually selected at the console when using _Secure , Mailflow, SharePoint, OneDrive and Teams applications.
Workaround
If you find you have special needs for your Finishing options then please directly connect to your printer over your LAN and use the latest HP Supported Windows Printer drivers.
Resolution
Under Investigation
Limitation
- When selecting Multiple jobs to print using the Universal Print Console (Secure), and each job has been printed under different Output side options, your print jobs will use the default settings for all selected jobs, for example if one job was printed using Duplex, and the next job was setup to print Simplex, and the Default Console Output Sides is set for Simplex, then all jobs will be printed as Simplex.
Workaround
Print each job individually and ensure you review the output option settings and adjust accordingly, this incudes if you want staples too.
Resolution
Under Investigation
Reported August 2025
HP Universal Print for Authentication Suite V3
Issue
Unable to register Printers Manually via the Universal Print Console app - Message Thank you for your patience, we are currently experiencing high demand. Please wait and try again later.
Work Around
Register Printers using the HP Command centre method, Click here for Install Guide
Resolution
Resolved in V4 October 2025 release
Reported March 2025
HP Secure Authentication Mobile app V1.5.0 on IOS
Issue
The first time you launch the Application on a iPhone using BLE to sign in using a RFIDeas BLE Reader, you may receive a BC01 Error message indicating to get closer and try again.
Work Around
Try a Second attempt, do not close the app, just tap the BLE Button.
Resolution
Resolved in the September 2025 release
Reported September 2024
Issue
You may see these 2 Error messages the first time the applications are installed when trying to launch, failed to get device token and Unable to retrieve data from HP cloud services.
Work Around
Close the messages, and try again, this should resolve the error messages, and if it does not then please refer to the following article What ports do I need to have open for Workpath apps
Resolution
Resolved in V4 and Recent Upgraded firmware 5.8.1.2
Other Limitation
We currently do not support Printing of Password protected PDF Documents in OneDrive, SharePoint and or Mailflow.
Resolution
Under Review.
HP Authentication Manager V3
We do not support 4.3" Screen sizes for HP Authentication Manager V3
However, if you wish to use our Universal Print application for Direct Print, Direct Print with Pin Code Release, Pull Print/Follow Me Print or using the Microsoft Universal Print Printed QRCode Secure release, then this is possible.
Our Next Release V4, which is due in October 2025 better supports 4.3" Workpath enabled printers.
Colour Printing
Your Monitor may not be calibrated to support RGB or Pantone color matching. As a result, the colors displayed on your monitor may not accurately match the printed output, regardless of your printer's brand or model.
Work Around
Here is one of our articles explaining the challenges, and possible workarounds, Click Here, else once HP releases a PSA driver, it may support ICC Profiles which could assist in colour matching, however there is no expected date for a PSA Driver.
Bugs
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article