No need to ensure Crypto object is non-null for SAML signature verification using a secret key

WSS4J currently throws an Exception if the Crypto object is non-null when trying to verify a signature, where the KeyInfo of the signature points to a SAML Assertion. However, for certain cases we query the CallbackHandler for a key, and so the check on Crypto can be delayed.