HP

HP multifunction devices are supported by OptimiDoc through the Open Extensibility Platform (OXPd). This page covers both HP Enterprise and HP Pro device types, describes how the integration works under the hood, outlines available features and authentication methods, and documents known limitations and firmware requirements.

HP is an embedded-terminal vendor: OptimiDoc installs an OXPd application on the device panel, can lock the panel behind authentication, release held jobs, run scan workflows, and account jobs via a device-pushed statistics agent.

Integration Method

OptimiDoc integrates with HP devices via the OXPd (Open Extensibility Platform) framework. OXPd enables third-party applications to embed custom user interfaces and workflows into HP devices. The OptimiDoc OXPd application provides:

• A login screen supporting card, PIN, and username/password authentication.

• A pull-print job list for releasing held jobs from the device touchscreen.

• Scan-to-workflow integration for server-managed scan templates.

The application is deployed remotely from the OptimiDoc web interface using the device's embedded web server credentials. OptimiDoc recognises two HP device models — HP Enterprise (HewlettPackard) and HP Pro (HewlettPackardPro) — and uses different OXPd endpoints and capabilities for each.

How the Integration Works

1. Installation

When you install OptimiDoc onto an HP device, OptimiDoc performs the following steps in order:

1. Certificate deployment — if the device is configured for a secure (SSL) connection, OptimiDoc imports the required certificates onto the device automatically.

2. Authentication and authorisation — if Device Authentication is enabled, OptimiDoc registers an OXPd authentication agent and an authorisation configuration (including any guest permission set), and registers the OptimiDoc login prompt as the device's sign-in method. If a card method is used, OptimiDoc registers the supported USB card readers as owned accessories so the device routes card taps to OptimiDoc.

3. Statistics agent — if accounting is used, OptimiDoc registers a statistics agent so the device reports job counters back to the server.

4. Application registration — OptimiDoc registers its top-level button(s) on the panel. On HP Enterprise with separate application registration, independent Print and Capture buttons are registered according to the device licence; otherwise a single OptimiDoc button is registered. Button icons are auto-sized to the panel by reading the device's UI attributes.

2. Authentication

The user authenticates at the panel via card, PIN, or login/password. On HP Enterprise, the OXPd authentication, authorisation, card, and statistics agents communicate over SOAP web services; on HP Pro they use a lightweight REST endpoint (/api/hp). When Single Sign-On is used without Device Authentication, the application passes the authenticated username to the panel automatically.

3. Job accounting (push-based)

HP accounting is event-driven: the registered statistics agent means the device pushes job statistics to OptimiDoc as jobs complete, rather than OptimiDoc polling the device. The agent is configured with a retry interval so counters are not lost if the server is briefly unreachable.

4. Remote login and logout

HP supports remote login/logout from the OptimiDoc web/mobile app. OptimiDoc reserves an OXPd authentication context to log a user in at the device, and releases the context to log out. (For HP, the authenticated state is confirmed by the device's own parallel sign-in requests.)

5. Uninstallation

Uninstalling removes the OptimiDoc top-level buttons (OptimiDoc, Print, and Capture), unregisters the statistics agent, clears the authorisation configuration, unregisters the authentication agent, and removes any registered card readers.

Authentication Methods

OptimiDoc supports the following authentication methods for HP Enterprise devices:

Separate Print and Capture Applications

HP Enterprise devices support separate application registration. The administrator can register independent Print and Capture (scan) applications on the device panel, allowing users to navigate directly to the desired function from the device's home screen. Which buttons appear depends on the device licence (Print and/or Capture).

SSL Certificate Deployment

HP Enterprise devices support automatic SSL certificate deployment. When the device is configured to use a secure (SSL) connection, OptimiDoc automatically deploys the required SSL certificates to the device during installation. This ensures encrypted communication between the device and the OptimiDoc server without manual certificate management on each device.

HP Pro Devices

HP Pro is a separate vendor type in OptimiDoc (HewlettPackardPro) with a more limited feature set compared to HP Enterprise:

HP Pro devices only support device-authentication methods (onlyDevice: true): PIN, Login and Password, Card, Card or PIN, Card or Login and Password, and — with Device Authentication enabled — External Authentication. They do not support Single Sign-On, User List, or the combined "Card and …" two-factor methods.

HP Pro devices use the Legacy terminal layout only, but do support terminal localisation, allowing the terminal interface language to be configured. When adding an HP Pro device, select HP Pro as the vendor type in the device configuration dialog.

Supported Models

LaserJet Enterprise Series

PageWide Enterprise Series

LaserJet Managed Series

Supported Features

Prerequisites

Before installing the OptimiDoc OXPd application on an HP device:

1. Ensure FutureSmart firmware. Only HP devices running FutureSmart firmware (version 4.10 or later) support OXPd. Devices with legacy firmware do not support embedded applications.

2. Enable OXPd on the device. Navigate to the device web interface > General > Solution Installer and ensure solution installation is enabled.

3. Enable HTTPS. The OXPd framework requires secure communication.

4. Configure SNMP for device monitoring. Set up SNMPv2c or v3 with credentials matching the OptimiDoc configuration.

5. Note the device administrator credentials for remote application deployment.

Known Limitations

• FutureSmart requirement: HP devices running legacy (non-FutureSmart) firmware cannot host the OptimiDoc OXPd application. These devices can still be used as print targets for pull printing but without the embedded agent (driverless pull print via IPP).

• OXPd version compatibility: FutureSmart 3.x devices support an older OXPd version with limited features. Full functionality requires FutureSmart 4.10 or later.

• Card reader compatibility: HP devices use a proprietary card reader interface. Ensure the card reader module is the HP-branded HIP2 (Hardware Integration Pocket) reader for guaranteed compatibility.

• Scan resolution limits: Some HP models limit scan resolution when using OXPd-initiated scans. Check the device specifications for maximum OXPd scan resolution.

• HP Pro limitations: HP Pro devices have a significantly reduced feature set compared to HP Enterprise. See the HP Pro section above for details.

Firmware Update Notes

HP FutureSmart firmware updates are generally backwards compatible with OXPd applications, but it is advisable to:

1. Test firmware updates on a single device before fleet-wide rollout.

2. After updating, verify the OptimiDoc OXPd application is still installed and functional.

3. Check for any new OXPd API changes documented in HP's firmware release notes.

4. If the OXPd application stops working after a firmware update, redeploy it from the OptimiDoc web interface.

In Summary

HP devices integrate through the OXPd platform. OptimiDoc deploys certificates, registers authentication/authorisation/card agents and a statistics agent, and installs one or more panel buttons. Accounting is push-based via the statistics agent, and remote login/logout from the OptimiDoc app is supported. HP Enterprise offers the full feature set (SSO, User List, separate Print/Capture apps, all layouts); HP Pro is limited to device-authentication methods plus External Authentication, on the Legacy layout only.

Related articles

• Managing Devices

• Device Communication Failures

• Supported Devices