I am just trying to implement a small application which can sign PDFs by using a private key from the user's windows-keystore. I noticed that iText incorporates the bouncycastle crypto provider which is incompatible with the default windows class for certificates:
System.Security.Cryptography.X509Certificate
Was it really necessary to rely on a third party crypto provider? IMHO this complicates using iText.
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
System.Security.Cryptography.X509Certificate is not compatible with Java. You have to use Java compatible security provider like BouncyCastle with iText.NET.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, but I don't get this: "System.Security.Cryptography.X509Certificate is not compatible with Java".
IMHO this sentence doesn't make any sense. Of course a .net class is incompatible with java - or did you mean J#? Any Java class needs a different VM/environment.
On the other hand an X509 certificate has several standardised representations. A conversion between different languages and even platforms is possible. So what exactly do you mean with "not compatible"?
> You have to use Java compatible security provider like BouncyCastle with iText.NET.
I would if I could but from the windows certificate store you can not get the private key (as long as it is not marked for export).
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
System.Security.Cryptography.X509Certificate is not compatible with both Java and J#.
>I would if I could but from the windows certificate store you can not get the private key (as long as it is not marked for export).
One of the sample code can be found in iTextSharp site. <http://www.nabble.com/Re%3A+iTextSharp-p609655.html>. I recommend you to use iTextSharp for a new project. iText.NET is for a people who want to use a common code between Java and .NET.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am just trying to implement a small application which can sign PDFs by using a private key from the user's windows-keystore. I noticed that iText incorporates the bouncycastle crypto provider which is incompatible with the default windows class for certificates:
System.Security.Cryptography.X509Certificate
Was it really necessary to rely on a third party crypto provider? IMHO this complicates using iText.
Jan
System.Security.Cryptography.X509Certificate is not compatible with Java. You have to use Java compatible security provider like BouncyCastle with iText.NET.
Sorry, but I don't get this: "System.Security.Cryptography.X509Certificate is not compatible with Java".
IMHO this sentence doesn't make any sense. Of course a .net class is incompatible with java - or did you mean J#? Any Java class needs a different VM/environment.
On the other hand an X509 certificate has several standardised representations. A conversion between different languages and even platforms is possible. So what exactly do you mean with "not compatible"?
> You have to use Java compatible security provider like BouncyCastle with iText.NET.
I would if I could but from the windows certificate store you can not get the private key (as long as it is not marked for export).
Jan
System.Security.Cryptography.X509Certificate is not compatible with both Java and J#.
>I would if I could but from the windows certificate store you can not get the private key (as long as it is not marked for export).
One of the sample code can be found in iTextSharp site. <http://www.nabble.com/Re%3A+iTextSharp-p609655.html>. I recommend you to use iTextSharp for a new project. iText.NET is for a people who want to use a common code between Java and .NET.