Requirements & Supported Environments
Last Updated: May 21, 2026
Third-Party Vendor Policy - PrinterLogic works with third-party products listed below—so long as the vendor continues to support them. However, when they reach “end of life” (as defined by the vendor), we can no longer support them. If this occurs, we suggest you upgrade to a newer version. We define third-party software support as “mainstream support,” not any extended support options a company like Microsoft may offer.
Security Compliance
To see full details about our compliance against global standards, certifications policies and more visit the Vasion Trust Center.
To view our Secure Configuration Guide for Vasion Automate Fed environments, refer to Secure Configuration Guide.
Allow Lists
Below are several lists of regional URLs that require Allow access for services, certificates, and features to work.
Filtering for Allow lists requires the URL and should happen at Layer 7 of the Firewall.
Use the recommended wildcard entries below, or see the Service Region URLs list to add each service.
- *.printercloud-fed.us
- *.app.printercloud-fed.us
- *.api.vasion-fed.us
- *.app.vasion-fed.us
Service Region URLs
The following must also be exempt from SSL Deep Packet Inspection (DPI).
|
URL |
Purpose |
|---|---|
|
{yourinstance}.printercloud-fed.us |
Primary gateway that allows the PrinterLogic Clients The Client is software that you install on a server or device that communicates with the PrinterLogic server. The Client installs and manages printers, driver profiles, and other settings. on your network to communicate with your PrinterLogic tenant (instance). |
|
{yourinstance}.app.vasion-fed.us |
Primary gateway for instances migrated to Vasion Automate. Handles services like Forms, Workflow, and Signature. |
|
printerlogic.printercloud-fed.us |
The Primary gateway for API calls across all instances, customer data is separated by client ID and a security token, and data is encrypted. |
|
agent-api.app.printercloud-fed.us |
The primary gateway for Service Client Any PrinterLogic Client-enabled workstation that has been promoted to provide one or more additional services that add specific functionality to the PrinterLogic environment (i.e., SNMP, iOS Printing, Email Printing, Printer Apps, etc.) communication. This includes advanced features like Vasion Output, Offline Secure Release Print, Off-Network Print, etc. |
|
agent-api-grpc.app.printercloud-fed.us |
The Output service uses Google Remote Procedure Call (gRPC), an open-source RPC framework built on HTTP/2, to maintain bidirectional communication with the Vasion gateway for print and service settings. This service requires that the environment support outbound HTTPS connections using HTTP/2. |
|
plat-api.api.vasion-fed.us |
API service that handles user authentication to the portals and changing/resetting passwords for customers who've migrated to the Unified Login. |
|
static-cdn.printercloud-fed.us |
Serves as the gateway for delivery of static assets, such as UI pages. |
|
gw.app.printercloud-fed.us |
Serves as the gateway for IdPs An identity provider (IdP) is a system entity that creates and manages identity information for an organization and can be authenticated by a computer system or network. An IdP is referred to as a security principal in Java and Microsoft documentation. An IdP also provides authentication services to relying apps in a federation or distributed network., SCIM A standard for automating the exchange of user identity information between identity domains or IT systems. SCIM uses standardized API throught REST with data formatted in JSON or XML, APIs A set of defined rules that enable different applications to communicate with each other, offering a service to other pieces of software., and Quota Management. |
|
cpa-api.app.printercloud-fed.us |
Serves as the gateway for Control Panel Application (CPA) A Control Panel Application (CPA) is an app that is installed on a compatible multifunction printer (MFP) and aids in the release of held print jobs, authentication for secure printing, and simple scanning functions. service. |
|
cpp-ui.app.printercloud-fed.us |
Serves as the Gateway between the Service Client, the user Interface for the CPA, and your PrinterLogic instance. |
|
cpp-api.app.printercloud-fed.us |
Serves as the gateway between the printer and the PrinterLogic instance for scanning features. |
|
ofn.app.printercloud-fed.us |
Serves as the main external gateway, where off network jobs will be received when using the |
|
ofn-gw.app.printercloud-fed.us |
Serves as a failover gateway for off-network print jobs |
|
oncp-ofn.app.printercloud-fed.us |
Serves as a gateway for Off-Network Cloud Print. |
|
oncp-pgw.app.printercloud-fed.us |
Serves as a gateway for the Off-Network Cloud Print app. |
|
oncp-ipp-gw.app.printercloud-fed.us |
Serves as a gateway for Off-Network Cloud Print. |
|
mobile-api.api.vasion-fed.us |
Gateway for the mobile app communication. |
|
client-api.app.printercloud-fed.us |
Gateway for Client communication. |
|
cdn.app.printercloud-fed.us |
Primary gateway for content delivery network - (AWS, CloudFront), and other static assets such as UI pages. |
|
print-api.app.printercloud-fed.us |
Serves as the gateway for Web Printing. |
|
edw.printercloud-fed.us |
Primary gateway for Enterprise Data Warehouse (EDW) A feature available for Web Stack and PrinterLogic customers. This feature is used to create custom reports using data from resources managed by PrinterLogic. This data can then be used with common Business Intelligence tools such as Crystal Reports, Domo, Tableau, and others.. Used to offload data for analytics. |
|
admin-api.app.printercloud-fed.us |
Serves as the gateway for feature flag communications with an instance. |
|
https://edge.microsoft.com/extensionwebstorebase/v1/crx |
Used to allow the installation of the Edge browser extension. |
|
https://clients2.google.com/service/update2/crx |
Used to allow the installation of the Chrome browser extension. |
|
https://pl-web-media.s3.amazonaws.com/extensions/printerlogic_extension-1.0.5.9-an%2Bfx-windows.xpi |
Used to allow the installation of the Firefox browser extension. |
CRLs and OCSPs
Because Amazon rotates the PrinterLogic certificate every six months, same issuing CA validity is not guaranteed for subsequent issuances. We recommend whitelisting http://*.amazontrust.com/* and http://*.digicert.com/* to prevent disruption.
- PrinterLogic Certificates
- Amazon Certificate
- Amazon Root CA 1 Certificate
- CRL:
- http://crl.sca1b.amazontrust.com/sca1b-1.crl
- http://crl.r2m03.amazontrust.com/r2m03.crl
- OCSP:
- http://ocsp.sca1b.amazontrust.com
- http://ocsp.r2m03.amazontrust.com
- CRL: http://crl.rootca1.amazontrust.com/rootca1.crl
- OCSP: http://ocsp.rootca1.amazontrust.com
- CRL: http://crl.rootg2.amazontrust.com/rootg2.crl
- OCSP: http://ocsp.rootg2.amazontrust.com
Off-Network Print
The options differ depending on whether you use the Vasion-hosted or a self-hosted external gateway.
- Vasion-Hosted External Gateway
- Self-Hosted External Gateway
Off-Network Print
- (YourInstanceURL)
- gw.app.printercloud-fed.us
- ofn.app.printercloud-fed.us
- ofn-gw.app.printercloud-fed.us
Off-Network Cloud Print (ONCP)
- (YourInstanceURL)
- oncp-ofn.app.printercloud-fed.us
- oncp-ipp-gw.app.printercloud-fed.us
- oncp-pgw.app.printercloud-fed.us
Off-Network Print
- (YourInstanceURL)
- gw.app.printercloud-fed.us
- And the Self-hosted gateway URL.
Mail Flow Rules
Certain features may require Mail Flow Rules to allow them to function as expected. Features using the email service include:
- Scheduled Reports
- Scan to Email
- Web Print (Allow Guests)
- SNMP Emailed Alerts
Email Sender (From):
Signed By:
Mailed By: Ensure you add the applicable regional URL from below to your inbound email allow list so that emails reach the user(s). PrinterLogic utilizes Amazon Simple Email Service (SES).
- US (printercloud-fed.us): us-west-2.amazonses.com
Supported Authentication Methods
PrinterLogic supports a wide range of identity providers for authentication and authorization within the product. Here are the supported provider options and their respective configuration pages for your reference.
An Identity Provider (IdP) provides user authentication and authorization to the consoles and features. PrinterLogic supports multi-tenant environments using multiple IdPs. Supported IdPs are:
Supported Mobile OS
The mobile app supports iOS, iPadOS, and Android devices.
- iOS / iPadOS: Supports the current and the previous OS version release.
- Android: Support follows the Android End of Life cycle. For more details refer to Android OS EOL.
Type 4 Drivers
Type 4 drivers do not work with TCP / IP printer objects with PrinterLogic because they turn off port monitoring, which the app needs. If a TCP / IP printer uses a Type 4 driver, it might cause printing issues. However, USB and software printers, such as Adobe and Microsoft XPS, can still use Type 4 drivers without problems.
Supported IPP Version
- 2.0
Printing with a mobile device requires access through two specific TCP ports: Port 631 and Port 80.
Client OS Hardware
The PrinterLogic Client supports the current and last release of Windows, macOS, ChromeOS, and Linux (Red Hat / Ubuntu) operating systems (OS). Vasion releases a new Client version that supports new OS versions within 30 days in Vasion Now environments. The following Scheduled Release SaaS (SRS) deployment includes the updated Client.
- PrinterLogic does not control the Client version in IGEL. Since the Client version may not always be the latest, it's important to recognize that each version has unique features and fixes.
- Client installation requires an operating system (OS) with a minimum of 300MB of free hard disk space. Printer drivers may require additional space.
- macOS devices using ARM processors may experience issues with some print drivers that lack native ARM support. Install Rosetta 2 for these print drivers to function correctly.
|
x86 |
x64 |
Other |
|---|---|---|
|
Windows 10/11 |
Windows 10/11/2016/2019/2022/2025 |
ChromeOS 109+ |
|
|
macOS 15 (Sequoia) macOS 26 (Tahoe) |
IGEL OS 11 IGEL OS 12 |
|
|
Ubuntu (LTS) 22.04 Ubuntu (LTS) 24.04 Red Hat 8 Red Hat 9 |
|
Chromebook OS Client
The ChromeOS Client is only compatible with the Google Identity service; it does not work with other Identity Providers (IdPs) An identity provider (IdP) is a system entity that creates and manages identity information for an organization and can be authenticated by a computer system or network. An IdP is referred to as a security principal in Java and Microsoft documentation. An IdP also provides authentication services to relying apps in a federation or distributed network..
You can find the Chromebook Client in the Google Admin Console listed as Extension ID: llhfdhidddepenjnklbngmapjohlbekh
Antivirus Exclusions for Client Stability
To prevent antivirus scans from affecting essential client components, please refer to the Antivirus Exclusions topic for a list of folders and sub-folders to exclude.
Supported SNMP Versions
If SNMP A Simple Network Management Protocol (SNMP) collects and organizes information about managed devices on IP networks and modifys that information to change device behavior. Devices that typically support SNMP include cable modems, routers, switches, servers, computers, printers, and more. is enabled, PrinterLogic leverages metadata to ensure precise reporting, SNMP information retrieval, Pull Print and Direct Secure Release functionality, and local user identities and email address synchronization. For a comprehensive list of the collected metadata and concise descriptions of their use cases see the Metadata Collected by PrinterLogic topic.
- SNMP v1
- SNMP v2
- SNMP v3
Supported Browsers
Vasion officially supports the current latest browser versions plus the previous version.
- Microsoft Edge (Chromium) 140, 141
- Safari 17, 18
- Firefox 140, 143
- Google Chrome 140, 141
Browser Extensions
- Edge (Chromium)
- Chrome
- Chromebook OS
- Firefox
Find the Edge (Chromium) extension in the Microsoft Store listed as the PrinterLogic Extension v x.x.x.x. Visit the Microsoft Edge (Chromium) Extension documentation for more information on installing it.
Prerequisites for Edge (Chromium) to function correctly:
- PrinterLogic Client version 25.0.0.481 or later.
- PrinterInstaller service version 5.0.6155 or later.
- Edge Browser version .88 or later.
Find the Chrome extension in the Chrome Web Store listed as the PrinterLogic Extension vx.x.x.x.
The Chromebook extension can be found in the Google Admin Console listed as Extension ID: llhfdhidddepenjnklbngmapjohlbekh
Open the Firefox browser and browse to https://vasion.com/browser-extension/ to install the extension.
Network Connection Ports
- General Ports
- Mobile App Ports
- Off-Network Ports
- Simple Badge Release Ports
|
General Features |
Description |
Source |
Destination |
Destination Port |
|---|---|---|---|---|
|
Printing |
Direct IP printing from the end workstation to the printer. |
Client/Workstation |
Output Device/Printer |
TCP 9100 |
|
Chromebook Printing |
Driverless IPP printing from the Chromebook device. |
Chromebook |
Output Device/Printer |
TCP 631 |
|
SNMP Monitoring |
Output Device/Printer monitoring and reporting. |
SNMP Service Client |
Output Device/Printer |
UDP 161, 162 |
|
Windows Printer Server Import |
Tool for importing printers into a new instance. |
Windows Print Server |
Instance/Client |
TCP 80, 139, 445 and UDP 137, 138 |
|
PrinterLogic Mobile App |
Description |
Source |
Destination |
Destination Port |
|---|---|---|---|---|
|
Direct IP |
Releasing "held" workstation print jobs using the mobile app. |
Client/Workstation |
Output Device/Printer |
TCP 9100 |
|
IPP Printing |
Printing directly from the mobile device using the mobile app. |
Mobile Device |
Output Device/Printer |
TCP 631/80 |
|
Off-Network Print |
Description |
Source |
Destination |
Destination Port |
|---|---|---|---|---|
|
Print Job Submission |
Printing from Off-Network Device. |
Workstation/Client |
Off-Network External Gateway |
TCP 443 |
|
Print Job Routing |
External Gateway Service connection to Internal Routing Service. |
Off-Network External Gateway |
Internal Routing Service Client |
TCP 443 |
|
Direct IP from Internal Routing Service Client |
Internal Routing Service delivery of print job. |
Internal Routing Service Client |
Output Device/Printer |
TCP 9100 |
|
Simple Badge Release |
Description |
Source |
Destination |
Destination Port |
|---|---|---|---|---|
|
rf IDEAS Ethernet 241 device |
rf IDEAS configuration |
Simple Badge Release Service Client |
rf IDEAS device |
TCP 23 |
|
ELATEC TCP3 device |
ELATEC TCP3 configuration |
Simple Badge Release Service Client |
ELATEC TCP3 device |
TCP 80 and 81 |
|
Device communication |
Communication between the badge reader and the Simple Badge Release Service Client |
rf IDEAS or ELATEC device |
Simple Badge Release Service Client |
TCP 31990 |
|
Direct IP printing from job release |
Direct IP printing after the badge reader triggers the job for release |
End user device or Client |
Output device or printer |
TCP 9100 |
CPA Manufacturer Support
|
Manufacturer |
Authentication Methods |
Multifunction Printers (MFPs) |
Badge Readers |
Features |
Install & Uninstall Ports |
|---|---|---|---|---|---|
|
|
|
|
TCP 8000 and 8443. |
|
|
|
|
|
TCP 443. |
|
|
|
|
|
TCP 58501. |
|
|
|
|
|
TCP 58501. |
|
|
|
|
|
SOAP 7627. |
|
|
|
|
|
TCP 50003. |
|
|
|
|
|
TCP 8083, 9090, and 9091. |
|
|
|
|
|
TCP 443. |
|
|
|
|
|
TCP 443 and 51443 (hybrid). |
|
|
|
|
|
TCP 80, 443, 10080, and 10443. |
|
|
|
|
|
TCP 10443, 49629, and 49630. |
|
|
|
|
|
TCP 443. |
*If you use a USB badge reader to release print jobs, some Canon models require you to turn on the Use MEAP Driver for USB Input Device option in the USB Settings section.
**You must configure badge readers as keystroke readers and include a carriage return value at the end.
CPA Supported Ports
|
Manufacturer |
Port |
|---|---|
|
Canon |
CPA installation and uninstallation occur between the Service Client and the printer over TCP ports 8000 and 8443. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Epson |
CPA installation and uninstallation occur between the Service Client and the printer over TCP port 443. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Fujifilm |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 58501. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Fuji Xerox |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 58501. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
HP |
CPA installation and uninstallation occur between the Service Client and the printer over Simple Object Access Protocol (SOAP) 7627. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Konica Minolta |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 50003. CPA operation requires two main communication paths:
Communication with WebDAV from the Service Client to the PrinterLogic instance over TCP 443. Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Kyocera |
CPA installation and uninstallation occur between the Service Client and the printer over TCP ports 8083, 9091, and 9090. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Lexmark |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 443. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Ricoh |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 443 and TCP 51443 for hybrid Android Java devices. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Sharp |
CPA installation and uninstallation occur between the Service Client and the printer over TCP ports 80, 443, 10080, and 10443. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Toshiba |
CPA installation and uninstallation occur between the Service Client and the printer over TCP ports 10443, 49629, and 49630. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. Communication for Simplified Scanning features occurs over TCP 50083 between the printer and the Service Client. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
|
Xerox |
CPA installation and uninstallation occur between the Service Client and the printer over TCP 443. CPA operation requires two main communication paths:
Everyday print communication occurs from the device to the printer over TCP 9100 or TCP 515 for Line Printer Remote (LPR) queues. By default Certificate Revocation List (CRL) checks occur over TCP 80 from the Service Client. The installation might fail if the CRL check cannot complete over port 80. |
Other
Import Windows Printers
- Administrator rights and access to connect to administrative shares (Admin$) on the print server are required to import printers from Windows print servers. Network ports to open between the print server and the importing computer include: TCP ports 80, 139, 445; UDP ports 137, 138.