I think it will be for another few months. The affected version listed in the report is 6.1.0 which has not even come out yet. So any update after that could have it fixed. We're now on 6.0.1. No idea what the release-cycle is for FMC.

I have the issue also. We have a wildcard certificate on the ASA but this does not get triggered because the FMC uses the ip address instead of the fqdn hostname.  The following bug report was created for this: https://bst.cloudapps.cisco.com/bugsea...