Cookie Encryption Key

[Ramon Pfeiffer]

>> I went ahead and disabled the use of the Cookie Encryption Key. On
>> startup, the error below is logged.
> 
> This is why I would advise you not to bother.

Meaning I can leave the Cookie Encryption Key as it is and also won't
have to bother about cycling it and syncing it between my cluster nodes?


> 
>> Apparently, in lines 168 - 176 of file system/conf/global-system.xml, a
>> default keystore of type JCEKS and with the alias secret is configured.
>> Can this be the cause of it?
> 
> There's a CAS bean that's depending on the keystore and it might not be possible to conditionally instantiate it. You can file a bug around making sure the documented process to disable this gets updated, but this is very, very low priority, there's simply no reason to worry about it.

I'll consider it.

Thanks again!

Ramon

--
Universität Tübingen
Zentrum für Datenverarbeitung
Wächterstraße 76
72074 Tübingen

E-Mail: ramon.pfeiffer at uni-tuebingen.de
Telefon: +49-7071-29-70213

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5217 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20170720/1798b1de/attachment-0001.p7s>