Genero OpenID Connect log file

The Genero OpenID Connect implementation produces a log file that helps to identify issues.

The log file is called OIDC.log and is located in $(res.appdata.path)/log. This log file contains all incoming and outgoing requests. It can help to debug OpenID Connect issues.

You can specify the level of detail recorded to the log with the

-debug
category

option of the OpenID Connect server program. There are two categories that can be logged individually or together:

MSG - Standard information regarding access and errors. By default, only access and error information are logged.
DEBUG - Traces the entire process of single sign-on (SSO).

To add debugging information to the OIDC.log, modify OpenIDConnectServiceProvider.xcf to include the -debug DEBUG option as first argument in the command defined by the MODULE element. In the following examples line breaks are added for readability:

<APPLICATION Parent="ws.default" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="https://4js.com/ns/gas/4.01/cfextws.xsd">
  <EXECUTION>
     <!-- Some ENVIRONMENT_VARIABLE entries removed for this example -->
     <ENVIRONMENT_VARIABLE Id="FGLPROFILE" Concat="APPEND">
       $(res.path.fgldir.services)/openid-connect/res/fglprofile
       $(res.path.separator)
       $(res.path.fgldir.services)/openid-connect/res/configuration
    </ENVIRONMENT_VARIABLE>
    <PATH>$(res.path.fgldir.services)/openid-connect/bin</PATH>
    <MODULE>OpenIDConnectServer -logPath "$(res.appdata.path)" -debug DEBUG</MODULE>
    <POOL>
      <START>1</START>
      <MIN_AVAILABLE>0</MIN_AVAILABLE>
      <MAX_AVAILABLE>10</MAX_AVAILABLE>
    </POOL>
  </EXECUTION>
</APPLICATION>

Note:

Logging is based on the Genero ERRORLOG() function. As several instances of the same OpenID Connect server can write to the log file, the PID of the server process is written to the log file as well.