DataSealer error

[Russell Beall]

Last minute testing and preparations have shown up another issue.  I've seen it from time to time but it seemed to be rare enough up until now.  Occasionally the crypto engine gets into a bad state and prevents any further logins from succeeding where the nameID was set to the crypto nameID.  This error shows up in the logs:
ERROR [edu.internet2.middleware.shibboleth.common.util.DataSealer:437] - Could not initialize cipher

And then subsequently, this happens:
Error resolving attributes for principal 'beall'.  No name identifier or attribute statement will be included in response

Earlier it seemed to be only on startup that if the first login failed, then I just had to restart.  Just now however, I saw it happen after the IdP had processed a few successfully, with CryptoNameIDs used, and then suddenly it started failing with no additional reason or information.

I have had to revert back to using the standard transient-nameID to move forward with the release.

I guess this is an issue mainly for Scott, but has anyone else seen this as well?

Regards,
Russ.