How to enable enhanced logging for the New Experience Admin Console

    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • Version Affected:  9.3, 19.07+


    How to enable enhanced logging for the New Experience Admin Console



    If there are New Experience Admin Console issues, in addition to the nlog from D:\Secureauth\ApplicationApi, it is also possible to enable an additional log.



    1. Create this folder if it doesn't yet exist:

    2. Backup this file:

    3. Edit the file D:\Secureauth\Api\nlog.config and replace the contents with this:


    <?xml version="1.0" encoding="utf-8" ?>
    <nlog xmlns=""
    xsi:schemaLocation=" NLog.xsd"
    internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log"> <!-- optional, add some variables
    <variable name="myvar" value="myvalue"/> <!--
    for information on customizing logging rules and outputs.
    add your targets here
    See for possible targets.
    See for the possible layout renderers.
    --> <!--
    Write events to a file with the date in the filename.
    <target xsi:type="File" name="f" fileName="${basedir}/logs/${shortdate}.log"
    layout="${longdate} ${uppercase:${level}} ${message}" />
    <target name="logfile" xsi:type="File" fileName="D:\SecureAuth\AdminApiLogs\AdminApiLog.txt"
    </targets> <rules>
    <!-- add your logging rules here --> <!--
    Write all events with minimal level of Debug (So Debug, Info, Warn, Error and Fatal, but not Trace) to "f"
    <logger name="*" minlevel="Debug" writeTo="f" />
    <logger name="*" minlevel="Debug" writeTo="logfile" />


    4. The new log will appear as D:\SecureAuth\AdminApiLogs\AdminApiLog.txt.

    5. When troubleshooting both the above file and the file D:\SecureAuth\ApplicationApi\nlog-all-YYYY-MM-DD.log should be used in conjunction and supplied together if requested by SecureAuth Technical Support.



    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.