There may be cases where Access Federation is not working as expected, and you would like to debug the problem.
You can enable the below debug logging in the $JFROG_HOME/var/etc/access/logback.xml. No restart is required for the logging to take effect.
Note: This is not the $JFROG_HOME/var/etc/artifactory/logback.xml file, the Access system has its own logging file under its etc folder.
<appender name="accessfederation" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${log.dir}/access-federation.log</File> <rollingPolicy class="org.jfrog.common.logging.logback.rolling.FixedWindowWithDateRollingPolicy"> <FileNamePattern>${log.dir.archived}/access-federation.%i.log.gz</FileNamePattern> <maxIndex>10</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>25MB</MaxFileSize> </triggeringPolicy> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="org.jfrog.common.logging.logback.layout.BackTracePatternLayout"> <pattern>%date{yyyy-MM-dd'T'HH:mm:ss.SSS, UTC}Z [jfrt ] [%-5p] [%-16X{uber-trace-id}] [%-30.30(%c{3}:%L)] [%-20.20thread] - %m%n</pattern> </layout> </encoder> </appender> <logger name="org.jfrog.access.server.rest.resource.system.communication.federation" additivity="false"> <level value="TRACE"/> <appender-ref ref="accessfederation"/> </logger> <logger name="org.jfrog.access.server.service.communication.federation" additivity="false"> <level value="TRACE"/> <appender-ref ref="accessfederation"/> </logger>
The above will create an access-federation.log file under $JFROG_HOME/var/log.