Skip to main content
Skip table of contents

Konica Minolta IWS Gen 2 Cloud Terminal with device locking (IWS Service Platform integration)


The feature is under KmIwsServicePlatformEmbedded feature flag

Card login is currently only supported if the Card Reader is set to Keyboard mode. (KM Mode, also known as Loadable driver mode, is not supported for now because of security reasons).

Prerequisites

  • License with a "KmIwsServicePlatformEmbedded" feature flag
    Verification can be done by scrolling down on the Overview page - in order to use the feature, it must be present under Account or Inherited features
  • IWS Service platform application is installed on the MFD (usually installed using KM Marketplace on MFD, valid KM Marketplace account needed)
  • KM Cloud terminal installed and configured (minimal version 2025.01.01, guide available here Konica Minolta IWS Gen 2 Cloud Terminal)
  • For automatic printer creation with automatic installation trigger, there must be no already existing printer with the machine serial number - if it already exists, manual change of printer embedded configuration to IWS Service Platform with manual installation trigger in its Deployment actions is needed (icon 
    )
  • Network visibility from MFD to cloud servers

Setup

  1. Open IWS Service PF application on the MFD


  2. Prepare configuration values for the next step to avoid machine logout timeout.
    You will have to enter the tenant domain three times, the API key of embedded type twice and change "Authorization Server Parameter".

    <customer-domain>: Go to Settings > Customer account and obtain a domain from the Domains list


    <embedded type API KEY>: Create a new API key under Security > API keys > Add, select embedded type, adjust other fields according to your security and note the embedded type API key down.
  3. Click on three dots in the upper left corner, open Administrator Setting, and Login by Administrator Password 
    (use the admin MFD password).
  4. Fill in the following fields and click save: 
    WebSocket Endpoint URL:  <customer-domain>
    WebSocket Endpoint Port: 443 (or 8715 if test environment does not support 443)
    WebSocket Password: <embedded type API KEY>
    Authorization Server Hostname: <customer-domain>
    Authorization Server Parameter: /ispf/v1/get_token
    Authorization Server Endpoint Port: 443 (or 8705 if test environment does not support 443)
    API Server Hostname: <customer-domain>
    API Server Port Number: 443 (or 8705 if test environment does not support 443)
    Client Secret Password: <embedded type API KEY>
    SSL Certification Check:  leave on True (or set False in testing environment)



  5. Login as an administrator to a web UI and check the Printers tab.

    There should be a printer with name MFD with IWS Service Platform <mfd-serial-number> which has assigned IWS Service Platform Embedded configuration.


  6. Go to the Embedded clients and select Deployment actions 
    for IWS Service Platform
    1. If the printer has the same machine admin password as default (1234567812345678) the Embedded is automatically installed and the MFD is locked.



    2. If the password differs the automatic installation fails and you need to change the Device admin password to the correct value in Embedded configuration > Device admin password


    3. You can configure "Type of login" here (Credentials or PIN).
  7.  If the Device admin password is set correctly, the MFD can be Locked by the Install and configure button and also Unlocked by the Uninstall button.

Troubleshooting

If these steps won't help, please contact support.


  • Printer is not created at all - possible causes:
    • Printer with the same serial number already exists, for example from Cloud terminal setup and usage:
      • Either change its embedded configuration for IWS Service Platform and trigger the installation under Deployment actions of the IWS Service Platform embedded template (icon 
        )
      • Or delete the existing printer and restart the MFD to trigger automatic creation again
    • Wrong domain in the configuration - check if it was entered correctly
    • Wrong API key in the configuration - check if it was entered correctly
    • IWS Service PF application was previously configured to a different environment - please restart the MFD after the configuration.
  • Printer is created, but cannot be installed:
    • Please see the exact message under Printers > Embedded templates > Deployment actions of the IWS Service Platform embedded template (icon 
      ), follow the instructions and manually trigger the installation from deployment actions again.

Limitations

General

  • Configuration to the secondary gateway server is not supported. 
  • The software logout button
     is not present. Logout is done only when the user clicks the HW logout button.
  • Language switching is not supported (will change in the future)

Authentication

  • Card authentication is active regardless of the chosen login method. It can be disabled by unplugging the card reader or turning it off in the MFD settings.

  • Card authentication registration is supported only in keyboard mode (KM Mode, also known as Loadable driver mode, is not supported for now because of security reasons - current IWS Service Platform limitation).

Accounting

  • If you are using KM IWS Terminal version 2024.11.01 and older with SQC version 2024.11.14 and newer the Copy job accounting from KM IWS Terminal will be doubled in Reports.
  • Native Scan and Native Print are not accounted (will change in the future)

Printing

  • USB printing is not restricted by USB print permission. Instead, it inherits the release job and colour print permissions for black-and-white and colour printing, respectively

3rd party limitations

KM IWS Service Platform

  • USB import - Currently not implemented feature.

KM Marketplace

  • Marketplace Copy - The copy operation failed without any further feedback. We are awaiting a response from KM support on how to proceed.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.