EJBCA accepts public RSA keys in CSRs, which are missing the "parameter" field, which should be NULL for RSA keys.

I can come up with two possible solutions to this:

• we could add a check of this before accepting the public key, perhaps by extending the new RsaKeyValidator class. For compatibility it should probably be an option, or it could break some clients (e.g. WS clients)
• we could simply ignore the "parameter" field and just put a NULL there in the final certificate. There's a small risk that this would cause compatibility issues, if someone expects the pubkey in the final certificates to have this non-standard format.