Advanced information security, traceability and mobility for Windows, Unix, AS/400, Mainframes,
SAP R/3, Oracle, Peoplesoft
and other ERPs.

 

Information:

Products:      

Home

Search

Contact us

 
Jetmobile > SecureJet 5 > SecureJet Print > SecureJet Box 


SecureJet Box


Secure Pull Printing for Legacy Printers

If you need to benefit from pull printing with legacy printers in your organization that do not natively support SecureJet Auth and Print-SMP module, connect them to  SecureJet Boxes with SecureJet Auth. Users can then use a PIN code, their corporate proximity badge or swipe card on the reader plugged to the box located next to the printer to release their print jobs retained in a SecureJet Print-PS server.

Authenticate on the reader or keypad to get your print jobs

SecureJet Box is a smart miniature print server connected to and located next to the printer.  Connectivity with the printer is through USB or network.

The SecureJet Box needs to be equipped with a SecureJet Auth-PX solution for authenticate the user using a badge reader or numeric keypad. Users authenticate using their PIN code or their badge, upon successful validation their pending jobs are instantly pulled from one of the remote SecureJet Print-PS print jobs retention servers and released on the local printer. 

An unlimited number of users can be recognized per SecureJet Box. The badge and users list can be validated live against LDAP or Active Directory* or against a users self-enrollment database.
*: Live LDAP/AD validation requires SecureJet Print-PS

The authentication process is very simple:

  • For PIN codes, the user enters his PIN code then press "enter" to release his print jobs
     
  • For badges, the user swipes or shows his badge at a distance of 0.5 to 2 inches (1 to 5cm, based on the badge type) to release his print jobs

Support SecureJet Auth modules are the following: Auth-PXT (PIN codes), Auth-PX (Proximity badges) and Auth-SW (Swipe cards)


Includes SecureJet Print-SMP in standard

Each SecureJet Box includes the SecureJet Print-SMP module, it does not need to be added to the box. Server-based retention requires additionally the SecureJet Print-PS server software. You will find more details about Secure Printing in the SecureJet Print-SMP and Print-PS information pages.



Badge number extraction and validation

When connected to the SecureJet Box, the SecureJet Auth module can validate badge numbers and get user information in various ways:

  • If the user Badge number is in Active Directory or LDAP database SecureJet can perform an indirect live validation of the user Badge number against that database. That validation is performed by SecureJet Print-PS authentication Windows service acting as a gateway.

    The user Badge number is submitted by SecureJet Print-PS to one or more AD/LDAP/SLDAP servers (failover capabilities) to find the user record matching the Badge number, with daisy-chaining capabilities. AD/LDAP/SLDAP returns the user information including his email address, login, full name, department name, domain, home folder etc.

    This solution is the best when user information is in LDAP/AD databases.


 

  • If users authenticate with proximity or swipe badges they can securely enroll and de-enroll their badge directly on a MFP or on a PC, without any support needed from IT or any email system (cumbersome and leading to significant support), and authenticate using the same badge on any SecureJet Box connected to the same SecureJet Print-PS. The enrollment PC must be equipped with a SecureJet enrollment software and the appropriate badge reader, MFPs must be equipped with a native SecureJet Auth-PX or Auth-SW solution (not connected to a SecureJet Box but directly to the MFP).

    To enroll users authenticate on the MFP or the enrollment PC against Active Directory or LDAP/SLDAP using their network login/password. They are requested to show their badge to the reader, the badge number is read, decoded and merged with the user Active Directory information.

    Enrollment information can be stored:

    • by the Print-PS server (does not require any database)
       

    • in a local or remote Microsoft SQL Server database
       

    • directly inside Active Directory or LDAP

    Once enrolled, users can authenticate with their badge from any SecureJet-equipped printer or MFP validating the badge against AD/LDAP or Secure Print Print-PS depending on the chosen storage.

    Once enrolled users can de-enroll even without their badge; they just need to authenticate on a SecureJet-equipped MFP or on an enrollment PC using their network credentials and request the de-enrollment of their current badge.



Usage on printers and MFPs connected to the SecureJet Box

Authentication on the SecureJet Box can be used for:

  • Print jobs release


Simple to install

SecureJet Box connect directly:

  • to any USB or 100BT ethernet Network printer. For network printers the box automatically reads the printer DHCP address, it features two bridged network ports so that you don't need any extra network plug on the wall.
     
  • to SecureJet Auth-PX, SecureJet  Auth-PXT and SecureJet Auth-SW authentication readers
     
  • to the corporate network in 100BT

 

All the software is running inside the diskless SecureJet Box. The Box is easily configured using a web browser with the address of the SecureJet Print-PS server performing authentication service and optionally the address of another server providing print jobs retention service.


System requirements

SecureJet Box supports most printers and MFPs with 10/100BT Ethernet LAN or USB connection.

SecureJet Box requires a SecureJet Auth PX, PXT or SW module to authenticate users.


Please read the SecureJet white paper for all information on pre-requirements
and special features

The SecureJet Box package includes

SecureJet Box
Power supply
Stand to put the box vertically
Setup guide

Regulation and compliance

CE and FCC Certified
WEEE and RoHS compliant

Part number: SJBOX001

 

 

    | (c) 2007 Jetmobile S.A.S | using this site means you accept its terms  | For questions about this site | last updated September 17, 2008 |