SHARP OSA Documentation

 

 

SHARP OSA
CONFIGURATION GUIDE
version 07.01.25

 

 

Background

Introduction

Prerequisites

Need to know

Adding a SHARP MX or BP device

Provisioning

  Configuring the External Authority Application

  Configuring the Standard Application

  Additional items to check

  Validating the provisioning process

  Post-Provisioning Configuration

    Authentication methods

    Additional Options

      Pull Print

      OSA Slot Number

   Device control (Authority)

Cloud-based Pull Print

  Background

  Prerequisites

  Configuring your queue

  iOS printing

    Configuring your queue for iOS printing

    Example printing workflow with Profile install

  Allocating and testing your Queue

    Google Workspace

    Microsoft Azure AD

    Internal directory users

Local Network Printing

Quota-based printing

  Creating a quota

Offline mode

Supported Device List

Troubleshooting Pull Printing

Job list not displaying

Text input not working on the login screen

Print Jobs not being held in the release application

 

Background

Sharp OSA (Open Systems Architecture) is a platform developed by Sharp Electronics Corporation that allows third-party developers to create custom software applications that can be integrated with Sharp multifunction printers (MFDs). These applications are designed to improve the efficiency and productivity of businesses by streamlining document workflows and automating repetitive tasks.

 

Sharp OSA applications are designed to be easy to configure, especially for IT professionals who are familiar with the Sharp MFD environment. 

 

The directprint.io administration console has in-built set-up wizards and tools that simplify the onboarding process of the OSA applications.

 

Introduction

directprint.io is integrated with SHARP OSA compatible MFDs with support for Sharp OSA 5 and 6 on BP and MX devices.

directprint.io’s OSA integration provides the ability to authenticate walk-up use of device-based functions such as print, copy, and scan. User or group-based policies allow for feature enablement and limiting.

 

Through directprint.io’s Cloud Edge pull print solution, users can release print jobs at any Sharp MFD that has been added to the queue. Print all, print and save, print and delete as well as setting advanced finishing options before printing are all available.

 

OSA Compatibility

 

Sharp OSA 5 and OSA 6 are the two most recent versions of Sharp's Open Systems Architecture platform. 

 

Not all Sharp MFD models support OSA, and some models may only support earlier versions of the platform. Therefore, it's important to check the specifications of your specific model to determine if it supports OSA 5 or 6.

 

directprint.io supports;

• OSA 5 (Browser n.2x)
• OSA 6 (Browser n.2x)

Please see the supported model list below. 

 

Authentication

• Card - Users can use a SmartCard reader to log in.
• User - Users can log in using their unique login ID.
• User & PIN - Users can log in using their unique login ID and PIN code.

 

Device Function Control

• Prevent unauthenticated use of the device. 
• Limit device functions (print, copy, scan) at the device level

 

Quota management

• Set page quotas (color, mono) at the device level
• Set page quotas (color, mono) to a specific group of users
• Set page quotas (color, mono)  to a specific user
• IT administration view on user remaining quotas and transactions
• User view on remaining quotas on device

Job Submission

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

Job Release

• Pull print (requires cloud printing)
  • Print all
  • Print & delete
  • Print & save
  • Set finishing options before print
• Direct print
  • Hold with a PIN
    • Print all 
    • Print & delete
    • Print & save
    • Set finishing options before print
  • Hold (no PIN)
    • Print all 
    • Print & delete
    • Print & save
    • Set finishing options before print
  • Print with no hold (job comes straight out with authentication)
  • Offline mode

 

Prerequisites

1. A Sharp MX or BP device supporting OSA application version 5 or 6 and Browser version n 2.x. See the supported device list.
   
   
2. SHARP MX / BP device will require the following modules;
   • Application Communication Module (ACM)
   • External Accounting Module (EAM)
     
     If your device(s) do not have these modules pre-installed, please reach out to your local SHARP supplier. 
3. A trial or licensed version of directprint.io RED.
   
   
4. The directprint.io Chrome application or the directprint.io universal driver for Windows or Mac.
   
   
5. Configuring directprint.io with Sharp OSA applications requires IP connectivity to the device. This can be done locally or via VPN.
   
   
6. To ensure a smooth onboarding experience, please ensure the device is configured to allow SNMP version 2 or above.

 

Need to know

directprint.io has two applications that require configuration on the SHARP
MX/BP models.

• The directprint.io External Authority Application
  • Responsible for access rights management to the device and associated functions.
    
    
• The directprint.io Standard Application - is responsible for;

• • Print release (direct print and pull print)
  • Quota display
  • Access to other device functions via the home button

 

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?

• User only - Users can log in using their unique login ID.

• User & PIN - Users can log in using their unique login ID and PIN code.

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

Do we require Sharp native drivers to work with directprint.io?
No, but you can use the SHARP native driver in combination with directprint.io and local network printing if you require it. 

directprint.io has a unique universal print driver that can be installed on Chromebooks, Macbooks, and Windows 10 / 11.

The universal print driver supports over 500 makes and models of Sharp workgroup and MFD print devices.

We support all advanced finishing features such as staple, hole punch, booklet, tray selection, etc., whether you're working with a workgroup or MFD device.

 

What if my customer wants to use directprint.io but not the OSA applications? 

directprint.io works with over 500 models of SHARP workgroup and MFD print devices independently from our Sharp OSA applications. We also support thousands of other print devices from other manufacturers. See our make and model support list here.

 

Adding a SHARP MX or BP 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;

 

5. If you select Automatic Scan skip to point 6. If you select Manual Scan, please enter.

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 Sharp MFDs then you will be presented with one expandable row with a Sharp 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 external authority application and standard application.

 

If for some reason the instructions on the web interface are not displayed, please follow the instructions below. 

Configuring the External Authority Application

1. Navigate to the devices administration console by entering the IP address of the device into your web browser.
   
   
2. Go to 'System Settings > Sharp-OSA Settings > External Accounting Application Settings'.
   
   
3. Enable the External Account Control option and check Set Authentication Server (Server 1).
   
   
4. Set the following;

• Application Name
  This can be defined by you but our default recommendation is;
  directprint.io external authentication
  
  
• Address for Application UI
  Each device you configure will have a unique code associated. XYZAB below is shown as an example.
  
  Please find the provisioning code through the link provided on the directprint.io administration console.
  
  https://red.directprint.io/api/sharp/v1/login.html?code=XYZAB
  
  
• Address for Application Web Service
  Each device you configure will use the same SOAP endpoint.

https://red.directprint.io/api/sharp/v1/soap

• Browser - HTML Browser n2.0
  
  

5. Reboot the device when prompted.
   
   When the device reboots the home screen of the device will be set to the directprint.io login screen.

 

Configuring the Standard Application

1. Go to 'System Settings > Sharp-OSA Settings > Standard Application Settings'.
   
   
2. Click Add and enter the following details in the registration form;

• Application Name: Edge Print Release (example)
• Address for Application UI: https://red.directprint.io/api/sharp/v1/cpa.html
• Timeout: 30 seconds
• Browser: HTML Browser n2.0
• Extended platform: Check

 

If you wish to use a custom logo for the application you can download the directprint.io RED logo from here.

 

Additional items to check. 

From OSA 5.5+  you must configure User Authentication in addition to the steps above. To do so, navigate to 'System Settings' -> 'Authentication Settings'.

Set 'User Authentication' to Enable and Authentication Server Settings to Sharp OSA.

 

 

Validating the provisioning process

When you have entered all the information, close the modal window. 

If the device is still waiting for a successful provision a ‘Pending Sync’ status will show in the Provisioned column of your MFD list.

 

Once the provision is successful a green tick will appear in the Provisioned column. Check the device, if everything is OK you will see a directprint.io RED logo and login screen on the device control panel.

 

Once the provisioning process is successful you may wish to validate the defaults set in the MFD configuration screen to ensure they match your requirements.

 

Post-Provisioning Configuration

Authentication methods

You have the following options available for authentication;

• None - No login methods using an ID or PIN are available
• User -  Users can log in using their unique login ID
• User & PIN - Users can log in using their unique login ID and PIN code
• Card authentication - Users can log in with their access cards. Card authentication can be used in conjunction with the options above.

Additional Options

Pull Print

To enable this device for Pull Print ensure the Pull print field is checked, this is enabled by default.

OSA Slot Number

When adding standard applications to your SHARP device they are assigned a slot number. The number entered into this value must match the number assigned to the directprint.io standard application number.

 

Device control (Authority)

directprint.io has exposed all of the Device control options from the SHARP MX and BP devices.

When provisioning an MFD for the first time we configure the device for a typical print, copy, and scan use case. 

 

If you wish to disable or enable specific features on the device then you can use the switches provided in the interface.

 

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 credentials (such as a username and password or 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 SHARP MX or BP device with the directprint.io External Authority and Standard 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

 

 

Example printing workflow with Profile install

 

 

 

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. If the user has a combination of cloud and local network jobs, both will be available in their print job list.

 

Configuring your printer to hold local network jobs

 

 

 

 

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

User ID by default is the first part of the user's Google Workspace email. This can be overridden in Google Workspace custom attributes using the attribute name MFD_USER.

Login PIN by default is the last four digits of the user's Google Workspace GAIA ID. This can be overridden in Google Workspace custom attributes using the attribute name MFD_PIN.

 

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 User ID is the first part of the user's Microsoft Azure AD email. Currently, this cannot be overridden.

By default the Login PIN is randomly generated based on the user's Azure AD SID. Currently, this cannot be overridden but can be found using the user search function.

 

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 Login ID and Smart CardID. These credentials can also be edited by editing the user record.

 

Quota-based printing

 

Quota-based printing refers to a system or approach where printing resources, such as the number of prints/copies are allocated to users or departments based on predefined quotas or limits. The purpose of quota-based printing is to manage and control printing costs, promote responsible printing practices, and reduce waste.

 

The directprint.io external authority application in combination with the directprint.io administration console can manage quota-based printing.

 

Creating a quota

1. Log into your directprint RED account https://red.directprint.io/admin using Google Chrome.
   
   
2. Go to MFD List - Quotas in the left-hand menu navigation.
   
   
3. Click ‘Add quota’ and fill in the form fields. 
   
   
4. Quota cycle - You can specify a quota cadence such as daily, weekly, monthly, etc.
   
   You can also specify the date on which you would like the cycle to start.
   
   
5. Quota targets - You can apply a quota on; 

• • Google OUs, groups, or individuals
  • Microsoft Azure groups or individuals
  • Internal directory groups or individuals

Quotas that are applied to OUs or groups will apply to each user within the OU or group. Therefore quota limits are not pooled between users.

6. Quota limits - limits can be set on how many pages (prints and copies) can be made for mono and color prints. Not setting a limit implies no limit / unlimited.
   
   
7. Quota features - Quotas can also be used to restrict specific functionality on an OU, group, or individual. Currently, you can enable or disable the following;

• • Stapling
  • Punching
  • Booklet
  • Binding
  • Saddle stitching
    
    

By default, these features are disabled when creating a quota. To enable the feature toggle the buttons to enable them. 

8. When you’ve finished filling in the Quota form details, click ‘Add quota’. 

 

Please note that once a quota has been created you cannot delete the quota however it can be edited.

 

If you have set a daily quote, please note that it will not take effect until midnight. 

 

Offline Mode

When using the cloud pull-print capabilities of directprint.io with your SHARP device there is a dependency on having a stable network connection so that users can authenticate against directprint.io's authentication service, download print jobs from the cloud, and be processed by the print device.

Occasionally there may be a time when your organization's external network connection goes down and cannot reach directprint.io's cloud service. In this scenario, end-users will likely still want the ability to print. With offline mode, this scenario is possible.

 

What's required?

On the SHARP device

1. Select the cache period of user information when offline mode is enabled. This enables user accounts to be cached on the device and to be used for authentication in a network outage situation.
   
   
2. For OSA 5.5+ you can enable offline mode through the authentication settings; as per the SHARP user manual;
   
   Enable Offline Authentication with stored User Information
   Allows the machine to be used in the event of a network failure, even when using network-based user authentication.

Admins must ensure end-users

1. Have a minimum of client version 24.01.03.0757m installed.
2. Be allocated the print device independently of the pull-print queue in the directprint client application
3. Have IP connectivity to the print devices
4. Have authenticated previously on the device
5. Decide whether they would like the jobs to be held and released after user authentication or have the job print straight out where authentication will still take place but the job will not be held. 

End users must

1. Submit print jobs directly to a specific print device (not the pull-print queue).
2. Login into the specific device by selecting their username from a list of users and entering their MFD login password (if jobs are set to hold).

 

Supported Device List

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.

 

Pull print status: % in bar	Interpretation
0%	Document download requested
33%	Job started to download
66%	Job queued to print
100%	Finished

 

The Standard Application settings do not allow 'Add' application

If you DO NOT see an 'Add' button in the Sharp OSA Standard Application Settings, you are likely missing a required Sharp module:

 

The Standard Applications setting screen should feature these options- note the 'Add button'.

According to the Sharp manual:

Please install the module before proceeding.

 

The standard application/job list is not displaying

HTML Browser n2.0

When configuring the external accounting and standard application your device should provide you with the ability to select a browser version. The two options that are typically available are;

• HTML Browser n2.0
• HTML Browser 3.5
  
  
  Browser selection in the Standard Application and the External Account Application configuration screens. 

Please ensure that you have HTML Browser n2.0 selected.

N.B

If the browser setting is not displayed then you must enable it through the administration console via

System Settings -> System Control -> Advanced Settings -> Click OK to proceed ->  List Display(J)

-> Enter ID 00001 or 00028 and click Show(N) -> Under Browser Setting select the Display option and then submit your changes.

Return to the Standard Application and External Accounting Application configuration screens and the browser selection will now be available.

Custom folders

Delete any custom folders that you have configured on the device before the installation of directprint.io

 

Text input not working on the login screen.

You will need to set  “Keyboard priority” to “Soft keyboard".

This can be found under System Settings -> Operation Settings

Reboot the device after changing this setting

 

Print jobs not being held in the Print Release Application (straight-out printing)

When you send a direct-IP print job (not via a Cloud queue) and the printer does not hold the job. Follow these steps below to fix this issue.

1. Go into the advanced config screen for the printer and add the ppd as shown in the screenshot below.
   
   
   
   
2. Set Enable Hold to force and enable
   
   
   
3. Refresh the directprint.io client and retry the print job.