Cert import failed....Could not parse the PEM-encoded import data
Things I've tried:
2048-bit and 1024-bit RSA keys
Encrypted and unencrypted keys
SHA-256 and SHA-1 signatures
v3 and v1 certificates
Bare-minimum certificates without any extensions
Subject Name fields matching Brocade defaults
LF and CRLF line endings
No line breaks at all
Is this feature even functional at all? Neither the Command Reference nor the Security Configuration Guide specify supported file formats, but my test cases have covered even the most legacy, compatible extremes without success.
I have, yes, but the filenames aren't the problem—the switch is successfully downloading both files, and the TFTP server's logs confirm this.
I tried enabling debug ip ssl, but no log entries are generated during the import process. Is there somewhere else I can look for debug info?
Can you post a sample key/certificate pair that successfully imports for you, and specify the switch model and FastIron version on which it succeeds? If your files fail to import for me, we can then narrow this down further.
I opened case # 01074612 but was rejected due to not having a support contract.
Considering how many different combinations of key and certificate types I've tried (all of which match what the documentation claims is supported), I'm very confident that this is either a bug or something that should be better documented—and in either case, the certificate import code should at the very least be printing more useful, granular error messages.
If this feature was implemented well, I wouldn't be needing support in the first place. Could you guys make an exception to the support contract requirement and see if this works on your end?