We are working on enabling MLE and during my testing, one of the tests I wanted to do was see what happens when we do a key rotation if a client was turned off for a while then gets turned back on. Now I know what will happen because I understand how MLE works but for the “uninitiated”, they wanted results to ensure they had proper instruction on how key rotation will be performed.
When I attempted to rotate keys, I suddenly got this error:
From my research on this error, it has to do with a SQL statement that may be trying to select something in a table that doesn’t exist. Obviously I can’t rewrite the admin tool so I’m wondering how we go about resolving this issue if anyone else has seen it before.
Okay so it seems reopening the BESAdmin tool when this error comes up will fix this error or, at least, that’s how I resolved the issue initially.
To attempt to recreate it, I tried doing the rotation again. Now I can’t even open the BESAdmin tool with an error stating the database is in an “inconsistent state” also stating the same error as above.
The problem is still on-going. After getting everything stable and key successfully switched, to document it I attempted to do it again. After an hour of waiting, the BESAdmin tool is still inaccessible and my clients are reporting this:
FAILED to Synchronize - IBM Endpoint Manager could not verify the authenticity of the site content. - class NoAuthorizedSignature (class CertificateRevoked)
Obviously this is a lot of work for a simple key rotation so something is amiss about this and I’m not sure what it is.
