Configuration

The Configuration option provides a tabbed interface to many standard configuration elements, stored on the server primarily in uf110d.ini, with some email-specific elements in the prog/mailcall.ini file and deliver.ini.  These are described in the Configuration chapter of the manual.  Note you can also manually edit either of these files on the server.

The following buttons are available: reload (the configuration settings), save, and server restart.  The server must be restarted after changes to the Server, Security, and TCP Ports sections.

When changes are complete, click the save button (a backup of the current uf110d.ini file is made as uf110d.ini.bak) and optionally restart the server.

Server

•Service port - the port the server listens on for client connections

•HTTPD port - the port the http/https server listens on for browser connections

•SSL options for both the Service and HTTPD servers.

•Certificate and private key paths used when SSL is configured for either server.  If not configured, a self-signed certificate is used.  Note the unform server/service user must have read access to these files.

•Directories - a list of directories searched for rule files and supporting files when print jobs run

•Purging - days the specified types of files and records are left on disk before automatically purged

•File Sync - if multiple print servers are in use, use these settings on the primary and secondary servers to define files and timing to sync from primary to secondary servers

•Archving Library Setttings - Define library settings and browser session duration

•Default rule file - if a job is submitted via the client without a -f filename option, this file is used

•Rebuild - if checked, when the server is started it will attempt clean up of control files to eliminate many types of corruption

Security

•Allowed IP's - IP addresses or wildcards that are allowed to connect to the server's main port

•Rule File Encryption - if checked, the design tool will save/publish rule files in encrypted format.  The UnForm server can use such rule files like any other, and the design tool can view/edit them, but a standard text editor cannot

•Auth Key - if specified, client configurations must supply a matching authkey

•Open ID Connect (OIDC) - define the settings used to utilize an OIDC provider's application registration for authentication.  

Email

•Mail Server - the SMTP server to use to send email, which may contain a port suffix, such as smtp.office365.com:587, or a ssl prefix, such as ssl:smtp.fastmail.com:465.

•Default From addresss - a From address to use if not provided in an email method

•Default Login, Password - authentication to login to the mail server.  The login account must have rights to send email on behalf of others if the From address of an email is different.  The password can be in two forms besides a plain text value:

ostore:name to use a password stored under name in Stored Passwords

ooauth:userid to use the Notes of the specified user as Oauth configuration information

•Test button - sends a test email using this configuration

Email Sending with Modern (OAuth2) Authentication

UnForm supports XAUTH2 authentication with a SMTP server, as well as traditional LOGIN authentication.  This requires configuring a dedicated user record with its Notes field filled in with text lines provided by the publisher through a registration procedure at https://unform.com/support/oauthcode.html.  The user record can be disabled to prevent its use other than as a secure storage location for the authentication data.

After registering an application with your mail provider, such as the App Registration pages at Microsoft 365's Azure Active Directory, you can visit the above web page to configure, authorize, and receive the tokens required for UnForm to perform this type of authentication.  Instructions are found at that page.

Once a user has been configured with the proper lines in its Notes field, you can specify which user contains the token information with a specially formatted password: oauth:userid.  For example, if you set up a user "z_smtp", use the password "oauth:z_smtp" in the email configuration for the source.  That format of password triggers the XAUTH2 authentication method.

The notes field should look something like this (lines here are truncated):

cid=2991095c-2b2a-4...

cs=Z2F8Q~5dZSM4v...

ep=https://login.microsoftonline.com/ab44...

tk=LCJhbGciOiJSUzI1NiIsIng1dCI6ImpT...

rf=0.ARIAlplEqxeM...

External Tools

•Ghostscript - the full path to the Ghostscript executable, typically "gs" on Linux/Unix, and gswin32.exe or gswin64.exe on Windows.  Use the latest version of GhostScript available.  Note that AFO requires Ghostscript 9.06 or higher.  If this is left blank, and a Windows Support Server is configured, UnForm will attempt to use a GhostScript configured in the Support Server, allowing a Windows version to be installed and used.

•Image Magick - the full path the the Magick "convert" or "convert.exe" program on the UnForm server.  If this is left blank, and a Windows Support Server is configured, UnForm will attempt to use the Windows Support Server for image scaling and conversion.

•GhostPCL - the full path to the GhostPCL executable, if available.  GhostPCL is used by the design tool for previewing PCL test prints on screen.

•OCR Service Key - if subscribed to the publisher's AI OCR service, enter the key here.

•Web Extension Rule Files - configure extension rule files for different URL patterns.

•Extension Printers - a list of name=settings lines.  The list is read by the UnForm Web Extension, a tool that provides an enhanced PDF viewer in a compatible web browser.  The names are presented in the extension, which can then submit that PDF file as an UnForm AFO job.

•Environment Variables - a table of custom environment variables to set when any jobs run

•Claude AI Settings - an API Key to use when submitting requests to the Claude API, and the API version (as of this writing, only 2023-06-01 is available).  The Claude API is used by the IDP module.  To keep the key value secure, the key itself can be stored in Stored Passwords under a name and the name referenced in the API key field with a "store:" prefix as "store:name".

TCP Ports

Enter the port configuration for network print capture.  More details on this feature are in the TCP/IP Monitor chapter.