Requirements
Supported Clients
The following clients are supported for sending print jobs to YSoft SAFEQ Cloud:
- Windows PC clients with Internet Printing Port enabled, on the following versions of Windows:
- Windows 8
- Windows 10
- Windows 11
- Windows Server 2012 R2 Remote Desktop Terminal Services Clients
- Windows Server 2016 Remote Desktop Terminal Services Clients
- Windows Server 2019 Remote Desktop Terminal Services Clients
- Mac computer clients
- macOS Mojave – version 10.14
- macOS Catalina – version 10.15
- macOS Big Sur – version 11.x
- macOS Monterey – version 12.x
- macOS Ventura – version 13.0
- Apple iOS devices, requires iOS 8.0 or later
- Android devices, Android OS version 5.1 or later
- Chrome version 44 or later for the Chrome extension
Supported Printers
For SAFEQ Cloud to send print job data to printers, a Document Output Service must be able to deliver data to the printers IP address on port 9100 or IPP (for more details see section Ports and Protocols below).
SAFEQ Cloud single driver capability is supported on the following vendors:
Vendor | Driver | ||
---|---|---|---|
PostScript | PCL6 | ||
Brother | ![]() | ![]() | ![]() |
Canon | ![]() | ![]() | ![]() |
FUJIFILM BI | ![]() | ![]() | ![]() |
HP | ![]() | ![]() | ![]() |
Konica Minolta | ![]() | ![]() | ![]() |
Kyocera | ![]() | ![]() | ![]() |
Lexmark | ![]() | ![]() | ![]() |
Ricoh | ![]() | ![]() | ![]() |
Sharp | ![]() | ![]() | ![]() |
Xerox | ![]() | ![]() | ![]() |
All FUJIFILM BI devices with Postscript are supported by default for Direct Printing (Push Print). Any device with AIP7 SDK, capable of running FUJIFILM BI Cloud Terminal can work without Postscript support.
YSoft SAFEQ Cloud can also receive raw print data streams from an IPP/IPPS client and deliver to a printer using any printer driver.
For more information on supported devices, see Hardware Compatibility List (HCL).
Ports and Protocols
The following is a list of possible ports used in SAFEQ Cloud. Ports required depend on the features, services and architecture used.
Communication occurs to/from a service, and the diagrams below serve only as a simple example, as services, such as Authentication Service, can be placed anywhere; in cloud, remotely, private cloud, on-premise etc.
SAFEQ Cloud uses TLS 1.3 for all internal communication (see Limitations for exceptions).
Server to Server
Port | Protocol | From | To | Description |
---|---|---|---|---|
2560 | TCP | Secondary SAFEQ Cloud Server | Primary SAFEQ Cloud Server | A secondary server communicating with the primary SAFEQ Cloud server for messaging exchange |
7300 | TCP HTTPS | Secondary SAFEQ Cloud Server | Primary SAFEQ Cloud Server | A secondary server communicating with the primary SAFEQ Cloud server API |
2552 | TCP | Primary SAFEQ Cloud server | Primary SAFEQ Cloud Server | A primary cluster server node communicating with other primary cluster server nodes |
8080 | TCP HTTP | Primary SAFEQ Cloud server | Primary SAFEQ Cloud server | Required for cluster node relay communication of UI requests |
Server to printers – print operations
Port | Protocol | From | To | Description |
---|---|---|---|---|
9100 | TCP | SAFEQ Cloud Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer |
631 | TCP HTTP | SAFEQ Cloud Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
443 | TCP HTTPS | SAFEQ Cloud Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
Server to MFD’s – embedded deployment
Port | Protocol | From | To | Description |
---|---|---|---|---|
161 | UDP | SAFEQ Cloud Terminal Client Service | Printer | SNMP management |
443 | TCP HTTPS | SAFEQ Cloud Terminal Client Service | Printer | Deployment of the embedded client to the MFD (all brands) |
80 | TCP HTTP | SAFEQ Cloud Terminal Client Service | Ricoh MFD’s | Deployment of the embedded client to Ricoh MFD’s |
8080 | TCP HTTP | SAFEQ Cloud Terminal Client Service | Ricoh MFD’s | Deployment of the embedded client to Ricoh MFD’s |
8451 | TCP HTTP | SAFEQ Cloud Terminal Client Service | Canon MFD’s | Deployment of the embedded client to Canon MFD’s |
51443 | TCP HTTPS | SAFEQ Cloud Terminal Client Service | Ricoh MFD’s | Deployment of the embedded client to Ricoh MFD’s |
8710 | UDP | SAFEQ Cloud Terminal Client Service | Ricoh, Lexmark MFD’s | Deployment of the embedded client to Ricoh and Lexmark MFD’s |
80 | TCP HTTP | SAFEQ Cloud Terminal Client Service | HP MFD’s | Deployment of the embedded client to HP MFD’s |
7627 | TCP HTTP | SAFEQ Cloud Terminal Client Service | HP MFD’s | Deployment of the embedded client to HP MFD’s |
10080 | TCP | SAFEQ Cloud Terminal Client Service | Sharp MFD’s | Sharp OSA communication, only for Sharp devices with embedded client |
50003 | TCP | SAFEQ Cloud Terminal Client Service | KM MFD’s | Konica Minolta OpenAPI communication, only for KM devices with embedded client |
8091 | TCP | KM IWS Install Tool | KM MFD’s | default port for installing IWS from the IWS Install Tool |
Embedded clients to server
Port | Protocol | From | To | Description |
---|---|---|---|---|
8700 | SSL | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients running on the Ricoh and Lexmark MFDs |
8703 | SSL | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients running on the MFDs (except Ricoh and Lexmark) |
8704 | TCP | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients running on the MFDs (except Ricoh and Lexmark) |
7301 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients running on the HP and Konica Minolta MFDs |
7302 | TCP HTTP | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients running on the MFDs |
7400 | TCP HTTPS | Printer | SAFEQ Cloud Authentication Service | Connection from the embedded clients to SAFEQ Cloud Authentication Service to register as trusted endpoints |
14080 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Connection from Equitrac server for embedded clients running on the MFDs |
14081 | TCP HTTP | Printer | SAFEQ Cloud Terminal Client Service | Connection from Equitrac server for embedded clients running on the MFDs |
14082 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Connection from the Ricoh SLNX Share embedded clients running on the MFDs |
14083 | TCP HTTP | Printer | SAFEQ Cloud Terminal Client Service | Connection from the Ricoh SLNX Share embedded clients running on the MFDs |
Web Administration UI
Port | Protocol | From | To | Description |
---|---|---|---|---|
8443 | TCP HTTPS | Client Web browser | YSoft SAFEQ Cloud Primary Server | HTTPS/SSL Web interface of the SAFEQ Cloud solution |
7290 | TCP HTTP | Client Web browser | EveryonePrint Mobile Print Server | Clients accessing the non-SSL Web interface of Y Soft Server. Default can be changed to standard http port 80 |
9443 | TCP HTTPS | Client Web browser | EveryonePrint Mobile Print Server | Clients accessing the SSL Web interface of Y Soft Server. Default can be changed to standard https port 443 |
PC clients to server
Port | Protocol | From | To | Description |
---|---|---|---|---|
2560 | TCP | SAFEQ Cloud PC Client | Primary SAFEQ Cloud Server | SAFEQ Cloud PC Client in ‘Local Storage’ mode communicating with the primary SAFEQ Cloud server for messaging exchange |
7300 | TCP HTTPS | SAFEQ Cloud PC Client | SAFEQ Cloud API Service | SAFEQ Cloud PC Client communicate with API to authenticate users and retrieve printers |
7300 | TCP HTTPS | SAFEQ Cloud PC Client | SAFEQ Cloud API Service | Clients sending standard print jobs to server |
7400 | TCP HTTPS | SAFEQ Cloud PC Client | SAFEQ Cloud Authentication Service | SAFEQ Cloud PC Client communicate with SAFEQ Cloud Authentication Service to register as trusted endpoints |
8631 | TCP HTTP | Client IPP | SAFEQ Cloud IPP Service | Clients sending IPP/http print jobs to server |
9631 | TCP HTTPS | Client IPP | SAFEQ Cloud IPP Service | Clients sending IPPS/https print jobs to server |
PC clients to printers – print operations
For SAFEQ Cloud PC Client in ‘Local Storage’ mode:
Port | Protocol | From | To | Description |
---|---|---|---|---|
9100 | TCP | SAFEQ Cloud PC Client Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer |
631 | TCP HTTP | SAFEQ Cloud PC Client Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
443 | TCP HTTPS | SAFEQ Cloud PC Client Document Output Service | Printer | An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
Mobile Print to server
Port | Protocol | From | To | Description |
---|---|---|---|---|
7910 | TCP HTTPS | Apple iOS clients | EveryonePrint Mobile Print Service | AirPrint print jobs from Apple iOS devices (secure) |
9444 | TCP HTTPS | Y Soft Mobile App | EveryonePrint Mobile Print Service | Authentication and document data from Apps (secure) |
Server to external authentication
Port | Protocol | From | To | Description |
---|---|---|---|---|
88 | TCP and UDP | SAFEQ Cloud Authentication Service | KDC | LDAP Kerberos authentication |
389 | TCP | SAFEQ Cloud Authentication Service | LDAP server | Connecting to LDAP server via LDAP (default port for LDAP) |
636 | TCP | SAFEQ Cloud Authentication Service | LDAP server | Connecting to LDAP server via LDAPS SSL (default port for LDAPS) |
443 | TCP HTTPS | SAFEQ Cloud Authentication Service | Microsoft Entra ID, OKTA, Google, PingID | Connecting to Entra ID, OKTA, Google or PingID via TLS/SSL |
Server to external database
Port | Protocol | From | To | Description |
---|---|---|---|---|
5432 | TCP | Primary SAFEQ Cloud Server | PostgreSQL Database | Connecting to external PostgreSQL database (default port for PostgreSQL database) |
1433 | TCP | Primary SAFEQ Cloud Server | MS SQL Database | Connecting to external MS SQL database (default port for MS SQL database) |
1521 | TCP | Primary SAFEQ Cloud Server | Oracle Database | Connecting to external Oracle database (default port for Oracle database) |
Embedded clients to Cloud Server or Gateway
Port | Protocol | From | To | Description |
---|---|---|---|---|
7301 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Connection from the embedded clients, HP Workpath Application and KM IWS, running on the MFDs |
7400 | TCP HTTPS | Printer | SAFEQ Cloud Authentication Service | Connection from the embedded clients to SAFEQ Cloud Authentication Service to register as trusted endpoints |
9444 | TCP HTTPS | Printer | SAFEQ Cloud Mobile Gateway Service | Connection from the embedded clients, HP Workpath Gen 1 Application and KM IWS Gen 1, running on the MFDs |
IP card reader to Server
Port | Protocol | From | To | Description |
---|---|---|---|---|
7300 | TCP HTTPS | IP card reader | SAFEQ Cloud API Service | IP card reader communicate with API to authenticate users |
7303 | TCP HTTP | IP card reader | SAFEQ Cloud API Service | IP card reader communicate with API to authenticate users |
SAFEQ Cloud Chrome Extension to Server
Port | Protocol | From | To | Description |
---|---|---|---|---|
7300 | TCP HTTPS | Chrome Extension | SAFEQ Cloud API Service | Chrome Extension communicate with API to authenticate users, retrieve printers and send jobs to SAFEQ Cloud |
Cloud terminal Integration to Server
Port | Protocol | From | To | Description |
---|---|---|---|---|
7400 | TCP HTTPS | Printer | SAFEQ Cloud Authentication Service | Cloud terminal integration – communicate with SAFEQ Cloud Authentication Service to register as trusted endpoints |
8705 | HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Cloud terminal integration (SQTS) – connection from Cloud Terminals running on MFDs (e.g. HP Workpath Gen2, KM IWS Gen 2, Ricoh Gen 2) and for sending scanned jobs (e.g., HP Workpath Gen 2, Ricoh Gen 2) |
8706 | TCP | Printer | SAFEQ Cloud Terminal Client Service | Cloud terminal integration – connection from Cloud terminals running on MFDs |
8707 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Cloud terminal integration – connection from Cloud terminals running on MFDs which provide scan data using SwA protocol (mainly Fujifilm BI terminals) |
8711 | TCP HTTPS | Printer | SAFEQ Cloud Terminal Client Service | Cloud terminal integration – connection from Cloud terminals running on MFDs which provide scan data using WebDAV protocol (KM IWS cloud terminals) |
Edge Gateway to Microsoft IoT Hub
Port | Protocol | From | To | Description |
---|---|---|---|---|
443 | SSL | Edge Gateway | mcr.microsoft.com | Microsoft Container Registry |
443 | SSL | Edge Gateway | *.data.mcr.microsoft.com | Data endpoint providing content delivery |
443 | SSL | Edge Gateway | *.cdn.azcr.io | Deploy modules from the Marketplace to devices |
443 | SSL | Edge Gateway | global.azure-devices-provisioning.net | Device Provisioning Service access |
443 | SSL | Edge Gateway | *.azurecr.io | Personal and third-party container registries |
443 | SSL | Edge Gateway | *.blob.core.windows.net | Download Azure Container Registry image deltas from blob storage |
5671, 8883, 443 | AMQP, MQTT, AMQP over WS | Edge Gateway | *.azure-devices.net | IoT Hub access |
443 | SSL | Edge Gateway | *.docker.io | Docker Hub access |
443 | SSL | Edge Gateway | *.ysoft.cloud | Platform |
2560 | TCP | Edge Gateway | Primary SAFEQ Cloud Server | A secondary server communicating with the primary SAFEQ Cloud server for messaging exchange |
7300 | TCP HTTPS | Edge Gateway | Primary SAFEQ Cloud Server | A secondary server communicating with the primary SAFEQ Cloud server API |
123 | UDP NTP | Edge Gateway | *.google.com (or anything else you will setup on the OMNI Bridge device) | NTP server (time{1-12}.google.com) or any chosen NTP server |