Riso directprint RED guide

RISO
CONFIGURATION GUIDE
version 03.07.25

Compatibility

Prerequisites

Need to know

Adding a Riso device

Provisioning

  Configuring smartcards

  Configuring Riso for directprint RED Application

  Additional items to check

    Authentication methods

Cloud-based Pull Print

  Configuring your queue

Local Network Printing

  iOS printing

    Troubleshooting

  Allocating and testing your Queue

    Google Workspace

    Microsoft Azure AD

    Internal directory users

Troubleshooting Pull Printing

Riso Compatibility

Please see the supported model list below.

Authentication

• Card - Users can use a SmartCard reader to log in.

Job Submission

• directprint.io universal print driver
  • Cloud-based pull-print

Job Release

• Pull print (requires cloud printing)

  • Print all
  • Print & delete
  • Print & save
  • Set finishing options before print

   

Prerequisites

1. A Riso device that is listed in the supported device list.
    
2. A trial or licensed version of directprint.io RED.
    
3. The directprint.io Chrome application or the directprint.io universal driver for Windows or Mac.
    
4. Configuring directprint.io with Riso application requires IP connectivity to the device. This can be done locally or via VPN.

Need to know

directprint.io has one applications that require configuration on the Riso devices
 

• The directprint.io Standard Application - is responsible for;

•  
  • Print release (pull print)

What identity providers (IDP) does directprint.io support?

• Google Workspace

•  
  • Sync directprint.io with Google Workspace for OU, group, device, or individual user printer allocation.
  • Use Google Workspace user information for MFD login.

• Azure Active Directory

•  
  • Sync directprint.io with Azure AD for Group and Individual user printer allocation.
  • Use Azure Active Directory user information for MFD login.
     

• directprint.io’s internal directory

•  
  • Create, update, and delete users and groups in directprint.io independently of any IDP.
  • Printer allocation can be performed against groups or individual users.
  • Create authentication-based user credentials for MFD logins.

Irrespective of the IDP you use, directprint.io allows you to add additional attributes to your users for MFD authentication such as login ID, PIN, and/or card authentication.

What login methods do you support?

• Smart Card - Use a SmartCard reader to log in.

Adding a Riso device

1. Log into your directprint RED account https://red.directprint.io/admin using Google Chrome.
    
2. Expand the Printer Network item in the main left-hand menu and navigate to Device Radar.
    
3. If prompted, install our Chrome, Windows or Mac application
    
4. Once installed, you will be presented with two options;

The IP address (or hostname) of the device or;

• A list of IP addresses (if adding multiple) or;
• An IP range (if you don’t know the specific IP addresses)

Then click ‘Scan for printers’.

6. When the devices are found, please click the ‘n found | continue’ button.
    
7. Assuming that you’re currently only adding Riso MFDs then you will be presented with one expandable row with a Riso header.

To see your devices list click on the expandable row. 

You can update the Printer name by using the pencil icon next to the input. Your changes will be saved when you add the device.

If you would like to see more information about the selected driver type and protocol used you can use the ‘Advanced options’ toggle.

8. If you’re happy with all of the displayed data and do not want to make any further changes please check the devices you wish to add and then click the ‘n selected | Add printers’.

If one of the devices you have added is in our supported device list then a modal will be displayed asking you to continue with the MFD provisioning process.

MFD Provisioning Process

Please follow the steps provided within the directprint.io RED web interface for the MFD provisioning process. This will guide you through adding directprint.io’s Riso application.

Configuring smartcards

To enable users to log into the directprint application on a Riso device, you must register their smartcards directly on the device.

1. Log in to the Riso device using the administrator account.
2. Go to Admin Menu > User Setting.
3. Select the user you want to register and Click on IC Card and register their smartcard.
4. Repeat Steps 3–4 for every user who will use the directprint application.

Configuring Riso for directprint RED Application

Follow these steps to set up your Riso device to work with the directprint RED application:

1. Access the Device Administration Console

• Open a web browser and enter the IP address of the Riso device.
• Log in as an administrator.

2. Configure External System Link

• Navigate to:
  Admin Menu → User Ctrl
• Click External System Link.
• Enter the required provisioning details from the directprint setup screen.
• Click OK to save the configuration.

3. Enable and Configure WebAPI

• Go to:
  Admin Menu → System
• Click WebAPI Settings.
• Set WebAPI to ON.
• Set the WebAPI Port to 8443.
• Under Password/IC Card Info Notification Method, select Plaintext.

4. Assign a Function Key to Launch directprint

• Still under Admin Menu → System, click Function Key Entry.
• Assign one of the available function keys to Browser.
  This key will be used to access the directprint application on the device home screen.

5. Update Printer Job Settings

• Go to:
  Admin Menu → Printer
• Click Waiting Job Setting.
• Set “Add all jobs received from a PC to Waiting Job List?” to No.

Additional items to check

To ensure directprint RED works, make sure each user's smartcard in directprint (under the Google Workspace or Entra ID tab via User Search) matches the smartcard registered on the Riso device.

Local Network Printing

Background

While Cloud based pull print is convient for allowing users to print from anywhere to any device in the queue, local network printing can still have advantages in some scenarios.

For example, if end-users are likely to always print to the same device (for example students in the art studio always print to the art studio copier) then there is no need to upload a print job to cloud and then have it downloded on the copier.

With this in mind, directprint.io supports the ability for end-users to print directly to the device if they wish. The local network jobs will be held on the device until the user authenticates on the device and releases them. For users to access local jobs they will need to use the native print app on the riso device. 

Accessing Local print jobs 

To access and release local print jobs on a Riso device, please follow the steps below:

1. Log in to the Riso device using the account that submitted the print job.
2. From the home screen, tap Storage, then select Load.
3. Navigate to the Personal folder.
4. Your submitted job should appear in the job list.
   From here, you can select and print the desired job.

Cloud-based Pull Print

Background

Cloud-based Pull Printing is a secure printing method that allows users to send print jobs to a Cloud-based print queue. The actual printing of the job only occurs when the user is physically present at the printer and authenticates themselves.

Instead of documents being automatically printed upon submission, users can "pull" their print jobs from any designated printer using their ID card This approach enhances security, reduces wasteful or unauthorized printing, and offers greater flexibility and convenience in printing workflows.

Prerequisites

To configure and utilize Cloud-based Pull Printing, you need at least one Riso device with the directprint.io RED application configured.

Configuring your queue

1. Log in to your directprint RED account at https://red.directprint.io/admin.
    
2. In the left-hand menu, navigate to ‘Edge Printing’ and then ‘Queues’.
    
3. Click the ‘Get started’ button to create your first queue.
    
4. In the modal window, enter a name for your queue, such as ‘New York office print queue.’
    
5. Choose your data storage region. For example, select ‘us-west-2 (Oregon)’ and click ‘Create’.
    
6. Once the queue is successfully created, the map will populate. Highlight the queue and click ‘Allocate printers.’
    
7. Select the MFDs that you want to allocate to the queue, and then click ‘Save changes’.

Allocating and testing your Queue

To test the queue you must provide end-users access to it. 

Google Workspace

You can allocate queues to Google OUs, groups, or individuals. Please see the instructions here on how to allocate printers/queues to users through Google Workspace.

Microsoft Azure AD

You can allocate queues to Azure AD groups, or individuals. Please see the instructions here on how to allocate printers/queues to users through Azure AD.

Internal directory users

You can allocate queues to internal groups, or individuals. Please see the

instructions here on how to allocate printers/queues to users through

directprint.io’s internal directory.
 

A user must sign in to the directprint.io universal print driver to install the queue. 

To test that the pull print queue is configured correctly, please send a test print to the queue from the user's device.

iOS printing

Configuring your queue for iOS printing

🛑 iOS Printing Not Working – Required Endpoint Whitelist

If printing from iOS fails or jobs don’t reach the printer, the issue is likely due to network restrictions blocking required IPP communication.

✅ Required: Whitelist These Endpoints

Ensure the following URLs are whitelisted (outbound HTTPS on port 443):

https://eu-west-2-ipp.driverlessprinting.com      # London
https://us-west-2-ipp.driverlessprinting.com      # Oregon
https://ap-southeast-2-ipp.driverlessprinting.com # Sydney
https://eu-central-1-ipp.driverlessprinting.com   # Frankfurt

These endpoints support iOS printing via IPP. Blocking them prevents print jobs from reaching printers.

🔍 Symptoms

• Print queue is not advertised in the printer list on iOS devices
• iOS jobs don’t print
• Jobs disappear or never appear in the users print queue
• AirPrint completes but no output

🔧 Resolution

• Allow HTTPS access to all the above domains in your firewall or content filter
• Test access by opening each URL in a browser on the affected network

ℹ️ Whitelist all regions if you manage roaming users or multi-region deployments.

For further help, contact support with device logs and network details.

MFD Authentication

The directprint.io External authority applications allow users to log in with either Google Workspace, Microsoft Azure AD, or directprint.io’s internal directory system. It is possible to mix and match all three of these directory systems if required.

See the authentication methods for the authentication options available.

Google Workspace

Smartcard ID by default is not set. To set it use the Google Workspace user search function. Alternatively, this can be set/overridden through Google Workspace custom attributes using the attribute name MFD_SMARTCARD_ID.

For overriding through custom attributes see the following support article on how to set custom data attributes through Google Workspace.
 

Microsoft Azure AD

By default, the smartcard ID is not set but can be set against the user through the user search function. 

Internal directory users

Follow the internal user directory setup instructions here.

When creating a user you can set a smartcardID. These credentials can also be edited by editing the user record.

Troubleshooting Pull Printing

When a pull print job is requested from the Cloud, the status bar goes through several steps.

The percentage related to these steps has a specific interpretation that can assist with debugging connectivity-related issues.