Publishing Authenticator

Lexmark Publishing Authenticator is a component used for the Single Sign-On (SSO) environment. It uses the Open ID Connect (OIDC) and Open Authorization (OAuth) protocols. User must install and configure this installer to enable SSO for Publishing Platform Manager and Publishing Solutions portals.

Note:  This product is optional and may be installed later in the environment.

Deployment readiness checklist

You can install Publishing Authenticator on a supported Microsoft SQL Server that runs on any of the following operating systems:

Before you begin, make sure that the following applications are installed on the server:

Setting up IIS

Make sure that the required server roles and features are installed or enabled.

  1. From the Server Manager dashboard, click Add roles and features , and then click Next .

  2. From the Installation Type section, select Role-based or feature-based installation , and then click Next .

  3. Select a server, and then click Next .

  4. From the Server Roles section, expand Web Server (IIS) .

  5. From the Web Server section, do the following:

    1. Expand Common HTTP Features , and then enable Default Document , Directory Browsing , HTTP Errors , and Static Content .

    2. Expand Health and Diagnostics , and then enable HTTP Logging and Request Monitor .

    3. Expand Performance , and then enable Static Content Compression .

    4. Expand Security , and then enable Request Filtering .

    5. Expand Application Development , and then enable the following options.

      • .NET Extensibility 4.5

      • Application Initialization

      • ASP.NET4.5

      • ISAPI Extensions

      • ISAPI Filters

      A screenshot of the options you need to enable in the Application Development section.
      A screenshot of the options you need to enable in the Application Development section.

  6. From the Management Tools section, do the following:

    1. Enable IIS Management Console .

    2. Expand IIS 6 Management Compatibility , and then enable IIS 6 Metabase Compatibility options.

  7. From the Features section, enable HTTP Activation and TCP Port Sharing .

    A screenshot showing the options you need to enable in the Features section.

Installing Publishing Authenticator

  1. Obtain the Publishing Authenticator installer.

  2. Run the LexmarkPublishingAuthenticator.exe file as an administrator.

  3. Read and accept the End-User License Agreement (EULA) , and then click Install .

  4. Click Next .

  5. Provide the fully qualified domain name (FQDN) or IP address of the SQL database server.

    Note:  If the database is running on a non-default instance name and non-default port, then provide the instance name.

  6. Provide the database server login ID and password.

  7. Select a database.

  8. In the Lexmark Publishing Auth Provider Configuration page, type the client ID and authority URL.

    A screenshot showing the fields in the Publishing Auth Provider Configuration page.

    Notes:

    • Client Id and Authority Url are required fields.
    • If you want to change the default scope value, then type it in the Scope field in comma-separated values.
    • If necessary, select the Enable Auto Provision check box.
    • For more details, refer to the PPR SSO Integration with Azure AD document.

  9. Browse to a folder where you want to save the Publishing Authenticator files.

    A screenshot showing how you can select the folder where the Publishing Authenticator files are stored.
    Note:  We recommend keeping the default directory.

  10. Install Publishing Authenticator.

FAQ

How do I change the database connection strings after installation?

The Database connection strings are stored in the encrypted form in the appsetting.json file, located at C:\inetpub\wwwroot\Lexmark_Publishing_Platform_Authenticator inside the ConnectionStrings:DataConnection key. Do the following to encrypt a connection string:

  1. Go to C:\inetpub\wwwroot\Lexmark_Publishing_Platform_Authenticator\ProtectConfigData.

  2. At the command prompt, type ProtectConfigData <ServerName> <DatabaseName> <UserID> <Password> .

  3. Run the ProtectConfigData.exe file.

  4. Replace the existing encrypted connection string inside the appsetting.json file with the newly encrypted connection string from the command prompt.