This document will walk through logs / screens related to three CA Strong Authentication component to try to find the root cause of the "No Transports Available" issue.
1. Arcot Flow Manager (AFM) log - arcotafm.log
2. Arcot Webfort log - arcotwebfor.log in DEBUG mode
3. Arcot Master Admin Console's" User Data Service Connectivity Configuration"
Webfort connects to UDS to retrieve the user that is being authenticated. If this is not possible the CA Strong Authentication processing will no complete.
CA Strong Authentication Servers
Note the arcotwebfort.log in DEBUG and Trace mode can lead to other reasons that could cause the "No Transports Available" issue.