Skip to content

Release Notes

5.3.4

New Features:

  • The script firewall.ps1 for Windows or firewall.sh for Linux is contained in delivery and can be used for opening the firewall ports required for Elastic Stack. For more information, refer to Configure the Management Server on Windows or Configure the Management Server on Linux.

  • The installation script for Elastic Stack on Windows has been changed from a batch file to a PowerShell script.

  • The default of the MONGO_LOCKS_AGE key has been changed from ten seconds (10s) to one minute (1m).

  • In the view configuration of the OIDC roles, the %ALLOWED_PRINTER_NAMES% value is available representing all printers which the current user can see. For more information, refer to Permissions and OIDC Roles.

  • The LOG_FULL_JOB_PROPERTIES key is available for specifying if the metadata of the jobs are logged.

  • The successful SAP notifications are logged with the log level info.

  • With the job metadata, only one attribute concerning the number of copies is displayed. For how the number of copies are determined from the input data, refer to Set the Copies.

  • The PostScript attributes are output to an additional file with the .psproperties extension when collecting all job files into a zip archive (via the download icon in PLOSSYS Administrator for example).

  • Node.js has been updated due to security vulnerability.

  • In PLOSSYS Administrator, the following new features have been implemented:

    • PLOSSYS Administrator has been updated to Angular 12.

    • In the dialogs displaying the job and printer logs, buttons are available for refreshing the contents.

Bug-Fixes:

  • Jobs paused on the source system are no longer fetched by the IPP Proxy.

  • When stopping PLOSSYS 5 on Windows, all services of SEAL Systems are searched and not only those in the "Running" status in order to catch all services in an "unclear" status as well.

  • The bug with collecting all job files including the temporary files into a zip archive (via the download icon in PLOSSYS Administrator for example) has been fixed.

  • PostScript properties without PLS_ prefix are interpreted correctly.

  • The audit log messages have been fixed.

  • The bug with hanging queues at high load has been fixed.

  • The housekeeper service no longer harm jobs which just have arrived.

  • In PLOSSYS Administrator, the following bugs have been fixed:

    • Autoreload has been fixed with all tabs.

    • The number of waiting jobs is displayed correctly now.

5.3.3

New Features:

  • The socketCloseTimeout printer key is available for specifying the timeout for closing the connection to the printer for each printer separately.

  • Node.js has been updated due to security vulnerability.

  • Ghostscript has been updated to 9.52.0.6.

  • The AUDIT_LOG key is available for logging audit messages, for example, the current configuration of each service. By default, audit messages are logged. For the further configuration, the AUDIT_LOG_USER and the JWT_USERNAME keys are available. When updating to PLOSSYS 5.3.3, the configuration in filebeat.yml has to be entered manually, refer to Update on Windows or Update on Linux.

  • The housekeeping has been improved in order to lower the system load with MongoDB.

  • Instead of outputting a job to a printer, a script can be executed with the spool data, for example, for sending an e-mail or copying the spool file to the file system.

  • The USE_ETAG key is available for deactivating the ETag handling.

  • In PLOSSYS Administrator, the following new features have been implemented:

    • Job watch tabs are created also for printers without having jobs assigned.

    • All statuses can be selected by one click in the status selection dialog.

    • The time filter has been improved.

    • The icon for the specific printer indicates if there are notes assigned to this printer.

    • The PRINTER_NOTE_ACTION_CONFIRMATION key is available for specifying if a confirmation dialog is opened with actions on printers for which notes exist.

    • The click-able area of the Web link to SEAL Systems has become smaller.

    • The log messages are displayed in one line and can be expanded for more details.

    • In the dialog for selecting the columns to be displayed, all columns can be selected by one click. The dialog stays open until the user closes it explicitly.

Bug-Fixes:

  • The bug that objects were output incorrectly in the log messages has been fixed.

  • The bug that jobs were fetched more than once if they were stopped on the target system has been fixed.

  • The crash of seal-controller after an error occurred with MongoDB has been fixed.

  • A fatal message is logged in case of a service crash.

  • The housekeeper service no longer harm jobs which just have arrived.

  • In PLOSSYS Administrator, the following bugs have been fixed:

    • The icon displayed for the remote processing status has been corrected.

    • The postponedpreprocessing status is displayed in PLOSSYS Administrator.

    • The bug when switching between tabs which were previously renamed has been fixed.

5.3.2

New Features:

  • As of PLOSSYS 5.3.0, the seal-dispatcher is available as replacement for the seal-controller service. With PLOSSYS 5.3.2., the seal-dispatcher service is no longer supported. The functionality of the seal-controller service has been integrated into the seal-controller, the seal-rest and the seal-convert-dispatcher services.

  • The service evaluating PRINT_ERROR_SHEET changed from the seal-dispatcher to the seal-convert-dispatcher service.

  • The service evaluating CONVERT_ON_PRINTER_START changed from the seal-rest to the seal-controller service.

  • JOB_RETRY_DELAY is available for specifying the waiting time between the postponements in case the next service is not available for example.

  • JWT_ROLES is available for specifying the property name set in JSON Web Token (JWT) for accessing the user roles.

  • AUTH_ADDITIONAL_SCOPES is available for specifying additional scopes for OAuth 2.

  • AUTH_TOKEN_TYPE is available for specifying the type of the token used for the authentication against the REST API.

  • ORPHAN_CHECK_INTERVAL is available for specifying the time interval between two checks for printers no longer locked by a seal-controller instance.

  • MongoDB is no longer included in the installation of PLOSSYS 5. For how to install and configure MongoDB, refer to the SEAL-specific MongoDB documentation. After the installation and an update, the MONGO_xxx_URL have to be checked for correctness, refer to Configure the MongoDB Keys in PLOSSYS 5.

  • The installation script for PLOSSYS 5 on Windows has been changed from a batch file to a PowerShell script.

  • If a CA certificate has been specified, the Output Engine services and all other components such as MongoDB and Consul require a client certificate from their correspondent client components. This would require corresponding properties of the certificate and would be a high effort. A complete explanation of how to use client certificates is beyond the scope of this documentation. The chapters containing the security configuration have been changed accordingly.

  • Setting the query parameter errorHandling to smart is no longer supported due to every connection interruption is ignored with this and every output job is considered as successfully output even if it was erroneous.

  • A printer template is available for converting a job into PDF in the preprocessing.

  • The messages in the job log in case of a redirected printer have been improved.

  • The times output with the log messages can be read by human beings.

  • For collecting output jobs, the collect privilege is available with ALLOWED_OIDC_CLIENTS.

  • With the output job, the name as it was passed to the system is displayed instead of an internal name.

  • The seal-ipp-checkin service can be accessed both using IPP and IPPS. For enabling this, two URLs can be specified with SERVICE_URL.

  • Via ?stream=false with the connection string, jobs can be output via LPR to a Windows Print Server, refer to the connection printer key.

  • Before updating the system, the checkin services have to be shut down gracefully. A description of how to do this has been added to the documentation: Graceful Shutdown

  • Via the REST API, secure database queries can be specified with options so that only the relevant data will be transferred.

  • The status of a job received via IPP Proxy is displayed in the source system.

  • sapgofu2pdf.exe used by seal-sapgof has been updated to the version 9.0.12.

  • The installation method of the services has been improved so that the installation is much faster and all directories are deleted correctly when updating or uninstalling.

  • Instead of outputting a job to a printer, a script can be executed with the spool data, for example, for sending an e-mail or copying the spool file to the file system.

  • IPP and SAP notifications are kept in the database. The seal-housekeeper service cleans out-dated successful notifications after the specified time, NOTIFICATION_LIFETIME_IPP and NOTIFICATION_LIFETIME_SAP.

  • A memory leak has been fixed.

  • Node.js has been updated due to security vulnerability.

  • The SOCKET_CLOSE_TIMEOUT and SOCKET_CLOSE_TIMEOUT_IS_JOB_ERROR keys are available for the seal-checkout service for forcing the closing of the socket after sending a spool file to the printer unless the printer closes the connection.

  • In PLOSSYS Administrator, the following new features have been implemented:

    • The user interface has been redesigned using PrimeNG.

    • When updating the printer status, a dialog containing the status information is opened. The data displayed in the table is updated when closing this dialog.

    • Redirecting printers and jobs have been made more user-friendly and is provided via the context menu now.

    • The dashboard of PLOSSYS Administrator has been secured. In order that the user can see the dashboard, the dashbord area has to be specified in the ALLOWED_OIDC_CLIENTS key. For more information, refer to ALLOWED_OIDC_CLIENTS.

    • The size of the log dialog is kept for the following log dialogs.

    • By zipping the application, the size could be reduced from about 10 MB to under 1 MB. This significantly reduces the loading time.

Bug-Fixes:

  • If the user calling PLOSSYS CLI does not have the privileges for executing an operation, such as starting or stopping services, a correct error message is output.

  • The bug with PRINT_ERROR_SHEET in version 5.3.0 has been fixed.

  • In case of multiple copies of a document running on an error, the error sheet is output only once.

  • The housekeeping has been revised. It no longer crashes when a spoolfile to be deleted has already been deleted by another housekeeper instance or when too many jobs have to be deleted at once.

  • The bug with generating the PostScript code for the error sheets has been fixed.

  • The bug with specifying an erroneous log level has been fixed.

  • The bug when outputting native jobs via IPP has been fixed.

  • The bug with multiple URLs in the connection key has been fixed.

  • The checkPhysical and update privileges are evaluated correctly and added to the documentation.

  • The printer name is everywhere displayed as specified using upper and lower cases. In PLOSSYS Administrator, the display name is displayed correctly and all operations are available.

  • The bug when sending a wrong MIME type with a job so that the printer did not accept the job has been fixed. The MIME type is now set to application/octet-stream so that the receiver will find out for itself what job format it is.

  • The seal-copier service no longer crashes when a job cannot be sent to the printer.

  • The ipp-checkin gets the document of the last conversion instead of the original file.

  • The seal-job-notifier service can handle misconfigured jobs whose SAP systems IDs contain blanks only.

  • In case of a cluster installation, only one reply is sent back to SAP.

  • If a job cannot be output for a longer time, a log message is written. Via the remove-printer-lock.sh script, the SEAL Systems support can fix the problem.

  • If the reply to SAP does not work, a log message is written for each affected job.

  • The housekeeper service no longer harm jobs which just have arrived.

  • In PLOSSYS Administrator, the following bugs have been fixed:

    • The bug that sometimes the job log could not be opened has been fixed.

    • In the table, the printer name item is shortened as all other parameters instead of being wrapped to the next line.

    • The server name in the cluster is logged as host.name in the job log.

    • The bug that a user without redirect privilege could resume a printer has been fixed.

    • The bug with auto reloading has been fixed.

    • The bug with resizing the columns in the job view has been fixed.

    • The bug that the global filter settings were lost when changing the tabs has been fixed.

    • The bug that the number of displayed elements changed after a while has been fixed.

    • The bug that the main page was empty when starting and had to be reloaded has been fixed.

5.3.0

New Features:

  • Node.js has been updated to 12.19.0.

  • Internet Explorer 11 is no longer supported.

  • In addition to the already supported operating systems, PLOSSYS 5.3.0 is supported on Windows 2019, SLES 15 SP2 and RHEL 8.2.

  • PDF Tools 3.5.1.3 is used with PLOSSYS 5.3.0.

  • For dispatching the jobs, the seal-controller service has been introduced which will replace the seal-dispatcher service in the next version. By default, the seal-dispatcher service is still used but you can already activate the seal-controller service by setting JOB_DISPATCHING to next. For update hints, refer to Update on Windows or Update on Linux.

  • The CONVERT_ON_PRINTER_START service key is available which specifies if waiting jobs are scheduled for conversion when the printer is being started.

  • The status of a device can be monitored via IPP if the device has an IPP interface. Unless specified, the monitoring IPP URL is determined from the printer's connection URL. For more information, refer to Configure the Device Monitoring.

  • The useCopier printer key is available which specifies if the seal-copier service is used for resolving the job copies by sending the document data multiple times to the printer. Normally, the job copies are resolved by the printer itself.

  • The jobMaxPostponedCount printer key is available which specifies how often a job for this printer will be postponed by the service in case the next service is not available for example. After exceeding the specified maximum of postponements, the job will be considered erroneous. This printer key overwrites the JOB_MAX_POSTPONED_COUNT service key for the specific printer.

  • In PLOSSYS Administrator, the following new features have been implemented:

    • PLOSSYS Administrator has been updated to Angular 11.

    • With the new PAGINATION_STEPS and PAGINATION_DEFAULT_STEP service keys, the selection menu for the number of items displayed in the lists can be specified.

    • With the new PRINTERS_METADATA and JOBS_METADATA service keys, columns can be added to the printers and jobs views. For more information, refer to Configure Additional Columns.

    • The status of the device can be displayed in an extra column and can be updated manually via menu item. The details of the device status are displayed in an extra dialog.

    • In the user interface, all items of the current page can be selected via a checkbox.

    • After the log-on, the last view is displayed instead of the dashboard.

    • If an operation takes a longer time, for example, when processing many items, a process bar is displayed.

    • A confirmation dialog is opened when adding more than 50 items to a list watch tab.

    • The Location, Comment and Department columns can be selected for being displayed but are deselected by default.

    • The PRINTER.DETAILS.config. prefix is cut with parameters having no translation assigned.

    • When redirecting a printer, the printer is stopped before.

    • For showing the log messages of jobs and printers, direct links to Kibana are provided which open new browser windows.

    • The icon font used in the user interface (Font Awesome) has been updated to the newest version.

    • The user profile is displayed in an extra dialog.

Bug-Fixes:

  • The printer name is case-insensitive now.

  • Syntax error handling of PLOSSYS CLI has been improved.

  • The bug with the SAP BC-XOM reply when deleting a job has been fixed.

  • In PLOSSYS Administrator, the following bugs have been fixed:

    • The delete functionality has been activated for jobs waiting for preprocessing.

    • The numbers of jobs in the different statuses are evaluated correctly in the charts displayed in the dashboard.

    • The order of the parameters is still the same after reloading the page.

    • The empty window after deleting a watch tab for printers or jobs is no longer displayed.

    • Some bugs concerning reloading have been fixed.

5.2.1

New Features:

  • The preprocessing, processing and postprocessing steps have been revised. Preprocessing consists of the analysis of the input file and the conversion into the metaformat (PDF) which can be processed by PLOSSYS 5. The processing consists of the formatting (scaling, rotation), the rendering (stamping) and the postprocessing (conversion into the format which can be processed by the output device).

  • The waiting status has been replaced by the preprocessing, waitpreprocessing and waitprocessing statuses.

  • For a better performance, the results of the processing steps are kept in the database and are used if a job has to be repeated with the same settings.

  • The seal-pdf2ps, seal-pdfstamp, seal-ps2pdf, seal-router and seal-sapgof services have been replaced by new ones or have become obsolete. They have to be uninstalled manually after the update.

  • For the preprocessing, processing and postprocessing steps, standard flows are provided which can be customized via customer-specific flows and user exits. The customer-specific flows will not be overwritten when updating PLOSSYS 5.

  • Via PLOSSYS CLI, flows can be listed, imported, removed and exported to a file. When being imported, the flows are checked for syntactical correctness.

  • Native queues are available. All jobs send to a native queue are spooled by PLOSSYS 5 without any conversion or other manipulation. A queue becomes a native queue by setting the nativeQueue queue parameter to true.

  • Native jobs are supported. A job becomes a native job by setting the document-format IPP parameter to application/vnd.plossys.native or by setting PLS_PLOTTYPE to NATIVE in the SEAL attributes with IPP or as PostScript property.

  • PostScript input files are only converted into PDF and back to PostScript if the files are generated by Adobe Acrobat and the output is a PCL 6 printer.

  • For a printer failover, more than one URL can be specified in connection with the printer configuration. The URLs has to be separated by blank. If the connection to a URL cannot be established, the next URL is tried.

  • The new versions Ghostscript 9.52 (Build Number 6), PDF Tools 3.5.1.2 and sapgofu2pdf 9.0.6 are contained in delivery.

  • Jobs in the preprocessing status can be canceled, deleted, paused and resumed.

  • When setting the query parameter errorHandling to smart in the LPR connection string, a job will be considered as successful as soon as all data have been sent. A missing ACK from the printer will not result in an error in this case.

  • PostScript files containing a PJL header at the beginning are recognized.

  • In PLOSSYS Administrator, the following new features have been implemented:

    • The framework Angular has been updated to the version 9. In doing so, the dashboard has been revised completely.

    • The user can reset the user interface to the defaults which means, for example, that the default columns are displayed and the column widths are set to the defaults.

    • The user can select which columns are to be displayed, for example, the column displaying the target printer with redirected printers.

    • The texts displayed in the user interface can be customized and new languages can be added.

    • With any printer, a note can be input, for example, when a printer is out of order due to maintenance. The note is displayed in a separate column. A tooltip shows the complete text when hovering over the column. It shows also the user who entered the note and the time when the note was entered.

    • A checkbox is provided for switching on an automatic reload of the printer and job views. The interval can be specified in the user profile individually. Default are 5 seconds.

    • In the job view, a link to the specified printer is provided. When clicking the link, a watch tab is created in the printer view containing the printer.

    • In the printer view, a link to the assigned jobs is provided. When clicking the link, a watch tab is created in the job view containing the jobs.

    • The user-specific settings (for example, the column selection and column widths) are additionally stored on the server so that the user has always the same settings, for example, when using another Web browser.

    • Like in all other columns, wildcards can also be used when filtering the printers.

    • Watch tabs can be created conveniently via context menu in the printer and the job views. Printers and jobs can be add to a watch tab or removed from a watch tab. Watch tabs can also be renamed.

    • The conversion results are provided together with the other job files when downloading the job in PLOSSYS Administrator.

    • Filters in the printer and in the job view can be saved as tabs.

Bug-Fixes:

  • jobid and uuid are logged correctly by all services and in all log levels.

  • The bug with the erroneous job count has been fixed.

  • If an error occurs within the conversion, an error message is output and the job is marked as erroneous.

  • In PLOSSYS Administrator, the following bugs have been fixed:

    • The language-specific translations have been added for some new job attributes.

    • The number of jobs waiting for a stopped printer is displayed correctly.

    • The details dialog stays open with the automatic reloading.

5.1.0

New Features:

  • With the version 5.1.0 of PLOSSYS 5, the directory structure of PLOSSYS 5 has been changed. Due to this, some steps have to be done manually when updating to this version. For more information, refer to Update on Windows or Update on Linux.

  • ELK has been updated to the version 7.6.0. ELK has been renamed to Elastic Stack and Logstash is no longer required. Also, Elasticsearch Curator is no longer required for purging Logstash indices. The installation of Elastic Stack for PLOSSYS 5 has two parts now, one for the management server containing Elaticsearch, Kibana and Logrotate and one for the Output Engine server containing Filebeat. For this, two different installation packages are provided.

  • MongoDB has been updated due to security vulnerabilities.

  • Node has been updated to version 12 due to version 8 is no longer supported.

  • The default authentication has been changed from Basic Auth/NTLM to OIDC.

  • The default authentication type and the allowed OIDC clients with default roles has been added to the default configuration file (plossys.yml).

  • PLOSSYS 5 recognizes PCL-5, PCL-6 and OTF (UTF-16 and ASCII) jobs.

  • PLOSSYS 5 recognizes ZPL jobs and routes them through without conversion by default.

  • After receiving the SIGINT or SIGTERM signal, the server tries a graceful shutdown by closing the TCP server for incoming new connections and waiting until all currently open connections are closed.

  • Consul is initialized only once and the configuration is passed to all modules.

  • The configuration of PLOSSYS 5 can be read from local files instead of Consul.

  • If the SERVICE_DISCOVERY environment variable is set to cloud, the seal-sapgof service reads the configuration from the local file instead of from Consul.

  • For the seal-sapgof service and the seal-pdfstamp service, the CONFIG_DIR environment variable is available for specifying a directory containing the configuration files, for example, when running PLOSSYS 5 without Consul in the cloud.

  • The seal-ipp-proxy service is available.

  • The seal-attributes tags contained in IPP jobs are now merged into the job object used by printer templates. If values are specified either in IPP and in the job, IPP takes priority.

  • The IPP operation Get-Notifications is available. With the notify-wait attribute, the connection stays open until the job is in a final state in order to get more notifications.

  • The IPP operation CUPS-Get-Printers is available for returning all printers.

  • Test jobs can be created via IPP. Therefore, printer names containing special characters (UTF-8) are possible.

  • With PLOSSYS CLI, the config update command is available, which is similar to config import but imports only those keys which do not exist yet.

  • PLOSSYS CLI can get HTPASSWD data from Consul, generate a template for this data and import it to Consul.

  • PLOSSYS CLI can get ALLOWED_OIDC_CLIENTS data from Consul, generate a template for this data and import it to Consul.

  • The PRINT_ERROR_SHEET environment variable is available which specified if an error sheet is output in case of error. Before, the error sheet was output in case of error, now the error sheet is not output by default but can be activated by setting PRINT_ERROR_SHEET to Y.

  • All tables with PLOSSYS Administrator have been redesigned.

  • Texts which do not fit into the column no longer overwrite the text in the next column but are displayed partly. The complete text is displayed in a tooltip when hoovering over it.

  • The service configuration file for the PLOSSYS Administrator service has been changed to /usr/lib/systemd/system.

  • In PLOSSYS Administrator, the roles received from the identity provider and the effective roles are shown.

  • IPP Checkin, IPP Proxy and IPP Checkout stream data directly into MongoDB instead of loading it into the memory.

  • For the seal-dispatcher service, the JOB_MAX_POSTPONED_COUNT environment variable is available, which specifies how often a job will be postponed in case the next service is not available for example. After reaching the specified maximum of postponements, the job will be considered erroneous.

  • Ghostscript version 9.27.0 is used by PLOSSYS 5.

  • PDF Tools version 3.5.1.1 is used by PLOSSYS 5.

  • sapgofu2pdf version 9.0.6 is used by PLOSSYS 5.

  • Message Server is supported with the job reply to SAP BC-XOM.

  • SAP NW RFC SDK 7.50 is supported due to version 7.20 no longer is supported.

Bug-Fixes:

  • The Output Engine status has been corrected for IPP status aborted.

  • Some bugs in PLOSSYS Administrator have been fixed, for example, the select button for printer and date in Internet Explorer.

  • The path of the Ghostscript binary has been corrected.

  • The bug with the fatal error message when starting ELK has been fixed.

  • The bug with JOB_LIFETIME_WAITING_PICKUP has been fixed.

  • ipp-checkin sets the compression-supported attribute correctly to none when an IPP client requested the attributes with get-printer-attributes.

  • The bug with printer names consisting of digits only has been fixed.

  • The UUID is logged by all services correctly.

  • The bug with handling special characters in the printer name has been fixed.

5.0.5

New Features:

  • Allow authentication via OIDC (JWT, Json Web Token) with PLOSSYS CLI.

  • OIDC password flow is supported for authentication as alternative to Basic Auth.

  • For PLOSSYS CLI, new commands are available for setting and getting values of configuration keys in Consul and creating templates for specific keys such as ALLOWED_OIDC_CLIENTS.

  • With PLOSSYS CLI, the value of the HTPASSWD key can be read from and writes to a file that is given with the HTPASSWD_FILE key for the Basic Auth authentication.

  • The pickup status has been introduced and is set correctly for new printers. With a pickup printer, the status cannot be changed. The jobs in pickup printer queues are not processed.

  • With JOB_LIFETIME_CANCELED, a time interval can be specified after which the canceled jobs will be removed.

  • With JOB_LIFETIME_WAITING_PICKUP, a time interval can be specified after which the jobs waiting in a pickup printer queue will be removed.

  • With the SHOW_ALL_JOBS_FOR_PRINTER key, all jobs of a printer can be displayed.

  • Basic Auth is available as user authentication.

  • The following IPP operations have been implemented: Hold-Job, Restart-Job, Validate-Job, Cancel-Job for a specific job-id, Get-Job-Attributes, Release-Job

  • Release-Job and moveJob have been enhanced in order to find the target printer with Secure&Pickup Printing.

  • Canceled jobs are hidden in the Get-Jobs response. This prevents the Windows printer queue from listing canceled jobs with Deleting status and thus confusing the user.

  • Attributes have been added to the Get-Printer-Attributes response for supporting the iOS printer profiles.

  • Secure&Pickup Printing is supported. Pickup queues are configured via the pickup=true queue parameter.

  • The version of Ghostscript is logged in the verbose mode.

  • Reading print data from database as buffer instead of a utf-8-encoded string allows sending binary data via IPP.

  • Jobs can be canceled. The cancelation is logged.

  • Via the MONGO_EVENTS_COLLECTION_SIZE key, you can specify the size of the capped collection for storing the events.

Bug-Fixes:

  • Every POST and PUT route is checked for valid permission. If the permission check fails, 403 is returned.

  • If authenticating with Basic Auth is used and no htpasswd file has been specified with the HTPASSWD_FILE key, authentication will never be granted. Before it was granted to everyone without checking the user and the password.

  • The canceled jobs are taken into account with the timeline statistics.

  • The current.seal-attributes.finalEventSent flag is set in the job properties correctly when the final status has been sent to SAP.

  • The bug with canceling jobs has been fixed.

  • seal-ipp-checkin no longer starts with an unsupported SERVICE_URL, ://localhost:631 or tls://localhost:631 for example. Now, an HTTPS server is started if the SERVICE_URL starts with https://... or ipps://... and an HTTP server if it starts with http:// or ipp://. If the Service URL is unknown, an error is output instead of starting the server.

  • The bug with activating TLS has been fixed.

  • The job-statusIPP attribute is set correctly if the job is in the canceled or aborted state.

  • The bug that jobs checked-in via IPP were mistaken as SAP notifications and repeatedly notified about has been fixed.

  • The copies IPP attribute correctly starts at 1 instead of 0.

Back to top