Hi Yamamo,

I haen't tried doing this in a pure Windows/.NET fashion yet, but I can tell
you what I have done when moving a cert/key from a UNIX environment to a
Windows environment.

I generated the certificate/key using something similiar to the instructions
for openssl found here:
http://code.google.com/apis/gdata/authsub.html

I then converted the key into the xml format used in .NET by using the tool
found here:
http://www.jensign.com/opensslkey/

I then used the RSACryptoServiceProvider.FromXmlString method to pass in the
<RSAKeyValue>...</RSAKeyValue> text.

Note- this is not an endorsement of the opensslkey tool or this method.  --
It worked well, but the cert I was creating was purely for test purposes and
I can't vouch for the security of this tool, and storing the private key
inside your code source probably isn't the best method :)  There appears to
be a way to store (and generate?) your key in the machine or user keystore..
That would probably be the best approach.

Determining the best way to handle this from within Windows/.NET is in my
list to do -- I'll post here when I have more information.  If others want
to post alternative solutions, I'm sure they'd be appreciated.

Cheers,

-Ryan



On 1/29/07, yamamo <[EMAIL PROTECTED]> wrote:
>
>
> Hi
>
> I want to use secure token authorization with .NET liblary.
>
> RSACryptoServiceProvider required to GAuthSubRequestFactory.PrivateKey
> property.
> But RSACryptoServiceProvider can not import private-key formatted by
> PEM.
>
> Please tell me,
> How should I generate X.509 Certificates and pass a private-key to
> RSACryptoServiceProvider ?
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to