Spring-Security-SAML & test-shib, Unable to encrypt, assertion

[Dan Turner]

Hi Ian,

Re-creating the keystore seemed to fix it. Keytool was behaving _very_
oddly; attempting to get info from keytool in this case (keytool
-printcert -alias skillsforgetrustfabrickey -keystore
sfTestKeyStore.jks) seemed to hang the keytool process (!).

I deleted the old keystore and re-created it:

keytool -genkeypair -keysize 2048 -keyalg rsa -validity 730 -keystore
sfTestKeyStore.jks -alias skillsforgeTrustFabricKey

Used the same passwords, etc. as specified in my configuration and it
mysteriously sprang to life after restarting Jetty &
re-requesting/re-registering my metadata.

Although I don't have a record of exactly how I generated the keypair
previously, I'm fairly certain that I used the same (or at least very
similar) method previously. Clearly I must've mis-typed something when I
setup the keystore in the past.

Regards,

Dan Turner

>> I am running a test system, with metadata registered at testshib.org,
>> and attempting a login. The redirect to testshib works as expected,
>> testshib accepts the myself:myself credential and attempts to encrypt
>> the assertions for return to our system, however, at this point it
>> falls over, with an Unable to encrypt assertion status message turning
>> up in our system's logs. From testshib's public logs:
>
> Is there anything unusual about the certificate you're embedding?
>
>    -- Ian