Ricoh multifunction devices are integrated with OptimiDoc through the Smart Operation Panel (SOP) REST API. The integration provides device authentication, print release, and a configurable landing-page experience on the device panel. This page describes how the integration works under the hood, the supported models and features, and known limitations.
Ricoh is an embedded-terminal vendor, but unlike most others it does not host a full OptimiDoc web terminal — instead OptimiDoc configures authentication and a landing page on the Ricoh Smart Operation Panel.
Integration Method
OptimiDoc integrates with Ricoh devices via the Smart Operation Panel (SOP) REST API at the /rws/sop/odauthinfo/ endpoint. The connection uses HTTP or HTTPS depending on the device's SSL configuration.
Installation pushes the authentication settings, card-assignment configuration, and landing-page preference to the device in a single POST request.
How the Integration Works
1. Installation
Installing OptimiDoc onto a Ricoh device posts a configuration to the SOP endpoint containing the OptimiDoc server URL, the authentication method, the card-assignment method, whether print-all is allowed (based on licence and the Print All setting), the landing-page choice, and the server context (device IP). OptimiDoc then verifies the configuration by reading it back and comparing each value.
2. Authentication and accounting
Users authenticate at the panel with a card, PIN, or login/password when Device Authentication is enabled; Single Sign-On is used when it is disabled. Copy accounting requires Device Authentication to be enabled (accountingRequiresDeviceAuth).
3. Landing page (no full web terminal)
Ricoh does not run the full OptimiDoc web terminal. After authenticating, the user sees the configured landing page on the Smart Operation Panel — the print-release view, a scan view, or a combined view.
4. Remote login and uninstall
Ricoh supports remote login from the OptimiDoc web/mobile app via the /rws/sop/odauthremote/ endpoint. Remote logout is not supported. Uninstalling is supported: OptimiDoc posts a request that returns the panel to cloud mode, removing the OptimiDoc authentication configuration.
Login reliability (26.07): The encrypted authentication ticket sent to Ricoh panels has been slimmed to fit within the device's HTTP header buffer limits. Previously, very long department names (or other long user fields) could inflate the ticket past the buffer and break login with "Invalid server response" / "Cannot reach server" even though the server had authenticated the user (OP-1437).
Monitoring reliability (26.07): SNMPv3 monitoring of Ricoh devices now handles time-window desynchronisation between the server and the device, preventing intermittent SNMPv3 authentication failures during device monitoring (OP-1192).
Supported Models
OptimiDoc supports Ricoh devices equipped with the Smart Operation Panel:
-
Ricoh IM series
-
Ricoh MP series (models with SOP support)
-
Ricoh SP series (selected models)
Supported Features
|
Feature |
Status |
Notes |
|---|---|---|
|
Pull print (release at device) |
Supported |
Card, PIN, or username/password authentication |
|
Copy accounting |
Supported |
Requires Device Authentication to be enabled |
|
Scan to workflow |
Not supported |
Native scan not available through the Ricoh integration layer |
|
Card authentication |
Supported |
Via SOP card reader integration |
|
Terminal application |
Landing page only |
No full web terminal; landing page is configurable |
|
Device monitoring (SNMP) |
Supported |
Toner levels, paper trays, page counts, error status; SNMPv3 supported |
|
Agent remote installation |
Supported |
Configuration pushed via SOP REST API |
|
Remote login |
Supported |
Via |
|
Remote logout |
Not supported |
— |
|
Remote uninstall |
Supported |
Resets the panel to cloud mode |
Authentication Methods
The User List method is not available for Ricoh. Single Sign-On is available only when Device Authentication is disabled; PIN and Login and Password are available in both cases.
|
Authentication Method |
Availability |
|---|---|
|
Single Sign-On |
Supported (when Device Authentication is disabled) |
|
PIN |
Supported |
|
Login and Password |
Supported |
|
Card |
Supported (with Device Authentication) |
|
Card or PIN |
Supported (with Device Authentication) |
|
Card or Login and Password |
Supported (with Device Authentication) |
|
External Authentication |
Supported (with Device Authentication) |
|
User List |
Not supported |
|
Card and PIN / Card and Login and Password |
Not supported |
Terminal Features
Ricoh devices do not support a full web-based terminal. Instead, OptimiDoc provides a configurable Landing Page on the device's Smart Operation Panel.
The landing-page setting determines what the user sees after authenticating:
-
Print release view
-
Scan view
-
Combined view
Localisation, terminal layout, and Legacy/Classic layout options are not available for Ricoh.
Prerequisites
Before installing the OptimiDoc agent on a Ricoh device:
-
Ensure Smart Operation Panel is available on the device model.
-
Choose HTTP or HTTPS. Ensure the selected protocol and port are accessible from the OptimiDoc server.
-
Configure SNMP for monitoring if required (SNMPv2c or SNMPv3).
Known Limitations
-
No full web terminal — Ricoh devices only support a landing page, not the full OptimiDoc web terminal interface.
-
No remote logout — the remote logout function is not implemented for Ricoh devices (remote login is supported).
-
User List authentication method is not available.
-
No native scan — scanning is handled through OptimiDoc's server-side scan templates rather than a device-native scan interface.
-
Copy accounting requires Device Authentication to be enabled.
In Summary
Ricoh devices integrate through the Smart Operation Panel REST API. OptimiDoc pushes authentication, card-assignment, and landing-page settings, and verifies them by read-back. Rather than a full web terminal, the user sees a configurable landing page after authenticating. Single Sign-On applies when the panel is unlocked; card/PIN/login and External Authentication apply with Device Authentication (which is also required for copy accounting). Remote login and remote uninstall (reset to cloud mode) are supported; remote logout is not.