Current implementation of checking SAS certificate against CRL may not start Configuration Controller when CRL resource is unavailable.
The functionality should work like this:
If there is anything wrong with getting the CRL list (CRL not specified in SAS cert extensions, CRL url not reachable available, CRL list corrupted etc) should result in starting the CC service and treat such situations as if SAS certificate would be valid (in a sense that it is not revoked)
Current implementation of checking SAS certificate against CRL may not start Configuration Controller when CRL resource is unavailable.
The functionality should work like this: