Also I am currently struggling to enable logging in the FederationPassive site. I've got the following in the web config (basically just uncommented what was there plus supplied a path for the log file) and I've grantedfull accesson c:\temp to Network Service. No log file is being produced.
<system.diagnostics>
<sources>
<!-- To enable tracing on a particular component, uncomment the desired section below. Then uncomment
the shared listener named "xml" and the Microsoft.IdentityServer.SourceSwitch in the switches element.
-->
<!-- Federation passive related tracing -->
<source name="Microsoft.IdentityServer.Shared.WSFederation" switchName="Microsoft.IdentityServer.SourceSwitch" switchType="System.Diagnostics.SourceSwitch" >
<listeners>
<add name="xml" />
</listeners>
</source>
</sources>
<!-- This is the shared listener for all of the tracing. All of the sources write to this listener.
If you want a more fine-grained listener, one can be added to the listeners element in each source above, which
can then output to different files if desired. After uncommenting this, put the absolute path of the trace file
ie c:\temp\TraceData.svclog. Be sure that the identity of the service can write to the file and directory -->
<sharedListeners>
<add name="xml" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\temp\TraceData.svclog" />
</sharedListeners>
<switches>
<!-- Uncomment this switch to use with your trace sources. You can add more and configure
them per source by editing the value attribute. For each source above, there is a switchName
attribute that links the source to a switch in this collection. You can use the same switch
with every source, or you can create a different switch for source for more control if thats
desired. -->
<add name="Microsoft.IdentityServer.SourceSwitch" value="Information" />
</switches>
<trace autoflush="true" ></trace>
</system.diagnostics>