Closed 978z3rzf89ou9jidejd0u93kjh8 closed 1 year ago
Can you contact support@pingcastle.com with the detailed log for both cases ? Indeed, there is no difference if you have a license or not during the audit phase.
While creating two new traces I remembered that I just copied the license file from the previous version instead of inserting the license string in the new license file from version 3.0. This did not affect the normal HealthCheck but it did affect the AzureAD check. After just copying the string to the file provided with version 3.0 all worked well.
So only my own fault of not using it correctly. Closing the issue and apologies for the trouble.
Since version 3.0 of PingCastle the AzureAD check crashes right at the start, when I use an auditor license. The issue goes away when I run the free version by replacing the config file. I have tested on multiple systems (all Windows 10 based) with multiple tenants and with both authentication methods (PRT & Ask). In the previous version the healthcheck did run with the same license without issue.
The trace.log, after running with the --log switch, looks as follows: