RSA AM doesn’t start after kernel upgrade?

If you’ve just upgraded the kernel and your RSA AM server doesn’t start anymore and you see the following error:

com.rsa.ims.security.keymanager.sys.SystemModificationThresholdException: System was modified beyond the allowed threshold, cannot decrypt.

don’t lose consciousness since there is a simple remedy for that

# su - rsa
$ cd /opt/RSAAuthenticationManager/utils/
$ ./rsautil manage-secrets -a recover
$ 

Just enter master pasword at the prompt and you’re golden.

6 thoughts on “RSA AM doesn’t start after kernel upgrade?

    • Hi Florian,
      My pleasure. It’s always good to know that there is a value even in this modest blog.

      Thank you.

  1. Of course there is, I also maintain a tech blog and no-one comment, ever, but there are readers and it doesn’t mean the content is not valuable.
    The value /is/ in the sharing. Even if it only helps one guy, that’s cool.
    I was digging deep into Oracle and java trying to remove old lock file and pidfiles before reading your entry which worked fine.

    Cheers.

    • What you’re saying is very true. That’s essentially why we all do post and share knowledge.

      RSA Authentication Manager is a quite complicated beast as it’s generally a mix of several products and technologies. And it’s uneasy at times to go through all of them to find the real culprit. Thankfully, when I first faced this problem, I had an access to knowledge.rsasecurity.com where I found the pill to fix my ache.

      Good luck with your blog, have fun.

      Cheers.

    • Hi Daniel,

      Good to know that this easy fix works for the Windows platform too.
      Thank you for sharing your experience.

      Cheers.

      Cheers.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.