1.5
Page 21
Scenario 2
Perpetual license with domain = "some.phantasy.com" and number of licensed users = 100.
Case 1: A job comes in from the domain “some.phantasy.com” and from a machine
named "KATERKARLO". The domain is right and this is the first job, so KATERKARLO is
added to the
UUSI
and handled in LICENSED mode.
Case 2: Meanwhile many, many users have printed from that domain, so all 100
UUSI
’s
(Unique User Slot Identifiers) are full (100 different machine names are in the list). A
user sends a job from a machine named "MICKEYMOUSE". This machine name is NOT in
the list. Connect checks the existing
UUSI’s
to see which one has not sent a print job for
the longest amount of time. Let us say, this machine has the name "DAISYDUCK".
o
Option 1: DAISYDUCK hasn’t sent a print job in the last 12 days. Since this is less
than 30 days the
UUSI
cannot
be released and so the incoming job from
MICKEYMOUSE is processed in UNLICENSED mode.
o
Option 2: DAISYDUCK hasn’t sent a print job in the last 42 days. Since this is
more than 30 days the
UUSI
will
be released and so the incoming job from
MICKEYMOUSE is processed in LICENSED mode.
Case 3: A job comes in from domain "starship.enterprise.it". This domain is not licensed,
so this job is considered an “unlicensed job” and will be processed in UNLICENSED
mode.
Security
In order to provide security when printing over the internet, OLCS includes several protective
features.
HTTPS Communication
The Printer Driver can be set to use HTTPS for any job transfer. To do this Workflow must also
be set to use HTTPS. This topic is covered briefly in the “Server URL Setting” section in this
document (new Printer Driver installation), but full details can be found in the Workflow
documentation.
Job Origin
Each print job will include unique information about the machine it has been sent from. This
unique machine ID is calculated with a proven method and will be transferred encrypted and
enhanced. The enhancement will result in a different encrypted machine ID per print job, so that
spoofing can be detected. On the server side, if spoofing is detected a respective messages will
be created.
Users can set up Workflow processes and filters to accept only specific jobs from known
machine IDs, thus enhancing security.
Database Connection
The OLCS plug-in works with a database to store all relevant job information. This database is a
“HyperSQL Database” (HSQLDB. See https://en.wikipedia.org/wiki/HSQL_Database_Engine). It is
installed as a service with the name “OL Connect Send DBServer” (the internal service name is
“OLCSServer”).