Note - some of these needs of authentication & client certificates will be 
added in iPhone 2.0, which is tipped to add "enterprise" capabilities.

SSL - support, yes - that works. Also email works well in IMAP mode for 
exchange servers that use certificate based authentication, without having to 
do any certificate settings on iPhone or server.

-Bhaskara


----- Original Message ----
From: Baglan Dosmagambetov <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, 14 May, 2008 7:57:12 PM
Subject: Re: Authentication and client certificates


I watched a video on ADC called "Leveraging iPhone Location,  
Acceleration, Orientation and System Information" (what a title :))  
and there it was said that one could access unique product number thru  
an API; however, I doubt there's a way a access that information from  
Safari.

I don't have an iPhone, but it, probably, can use SSL - so  
infrastructure for using certificates should be in place.

- Baglan

On May 14, 2008, at 7:48 PM, anmldr wrote:

>
> I sent you an email.  The only suggestion that I found on this group
> was to use a cookie.  But this does not prevent someone else from
> "sharing" their user name and password.
>
> If someone else has a suggestion that would be iPhone specific, for
> instance capturing the telephone number of the iPhone, I would be very
> grateful.
>
> Linda
>
>
> On May 14, 3:17 am, [EMAIL PROTECTED] wrote:
>> Does anyone have any information on installing and using client
>> certificates with the iPhone? I'd like to control access to a web  
>> site
>> by inspecting the client certificate.  Any help or pointers would be
>> greatly appreciated.
>
> >



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" 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/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to