wrong x509 instructions?

[Velpi]

Just wanted to let the community know that CAS 3.0.5 is doing fine in 
production, but mind these changes when upgrading:
* the new HttpClient does not allow * certificates
* because of the new spring version you need to change the value-key for the 
"lt" input field in you custom casLoginView.jsp from ${flowExecutionId} to 
${flowExecutionKey}

The RADIUS and X.509 authenticationHandlers that are scheduled for CAS 3.0.6 are 
also functioning properly. Also the initial CredentialsToLdapPrincipalResolver 
seems to function properly in a limited live situation.

-- Velpi