Identity Certificate not installing properly on OS 3.0

I have the following problem with the issue. Yes, there are some ways and tools to downgrade the baseband, for example. There are some utilities around to hack your iPhone completely. At the same time, I don't want to use them at all! I want to have a reliable device supporting some basic functionality to access corporate resources. Can I rely on a hacked iPhone? Definately not. So, I'll be waiting till an official fix is ready.

reliability did you say, I think not, if you cannot get your email functionality and apple may or may not be working on a fix.

I have seen several posts of some people from the same companies using the same exchange servers some who upgraded to 3.0 worked just fine, others now cannot get access to the exchange data (I say this because my iphone verified the exchange account settings successfully, so that means my information was entered correctly on the Iphone). If two people who both upgraded to os 3.0 are trying to connect to exchange and one can and one cannot, can't the one who couldn't use the other persons phone change the settings to thier account and show apple that this is either a hardware or operating system issue.

So anybody able to check if this is resolved in 3.1 beta 2?

Just to be clear, this is definitely not an Exchange issue. I do not use exchange. I am having the problem trying to connect to a selection of websites (each requiring different certificates) through safari.

The cert shows as blank when viewing from Stettings>General>Profiles, but I notice that I can see all the details correctly if viewing it from the VPN settings section (Settings>General>Network>VPN) and assigning it to a new VPN IPSec connection.

Therefore, it must be the certificate handling for Safari that is broken.

Can somebody please add the phone number, email address and links for the apple iphone support to this thread. Then we can all make our voices heard easier. I'm sure that we could look them up ourselves, but what with humans being inherently lazy, it's not likely to happen ;O)

I used the phone number posted here:

http://www.apple.com/support/contact/

I really liked the following article:

http://lists.foaf-project.org/pipermail/foaf-protocols/2009-June/000642.html

It fully reproduces and describes the problem.

@Pushtuk - Nice find. That sheds a little more light on things. So the iPhone is not actually sending a certificate, even though it asks you to select one. It still remains to be determined if this is a problem with safari, or a problem with the OS certificate store (in that safari cannot send the cert because when it reads it from the cert store it comes back blank).

Whatever the problem is, I cannot imagine it being more than a 10 minute job to fix. The difficult part is getting it high enough up the priority list for Apple to actually look at! Sigh...

Did Apple push out any updates to 3.1 to the testers that fixes this issue?

I've tested both OS 3.1 Beta 2 and Beta 3 and the certificate authentication problems are resolved for WiFi and ActiveSync.

Thank you for the good news!

An idea of the 3.1 release date ?

We've been told end of September. But I cannot speak with any accuracy for Apple.

Therefore, it must be the certificate handling for Safari that is broken.

In your use case, yes. My guess is the API to invoke and retrieve certificate data is broken, given it occurs in both Safari and Exchange pushmail sync.

Simon

@Corporate Guy - Thanks for testing and letting us know. I shall await the release of 3.1.

I was screwed over by this bug again today. I needed to access one of my secured sites from out of the office to fix something for a customer, but thanks to this bug had to travel all the way back to the office instead! 30 minutes of my life wasted.

Similar problem here. My iPhone worked fine with exchange before upgrading to 3.0. Here's the funny thing though - my colleagues and I here on the east coast who use iPhones have had no luck after the upgrade. However, my colleagues in other parts of the country who work with the same company and use the same iPhone exchange setups have no problems connecting to exchange and receiving email, calendar and contact info.

I travel a lot for work and I've found my iPhone will connect to exchange without issue in Denver, Minneapolis, Seattle and Dallas. Basically all other time zones but Eastern. I'm not sure how this relates to certificates but thought I'd mention it in case others have noticed the same.

We are still seeing this issue (or a very similar one) with OS 3.0, 3.01 and 3.1 on both 3G and 3GS handsets.

3.1 gives an error - "Authentication verification failed".
3.0/3.01 spin the busy wheel without providing any information.
2.x works flawlessly

This is all with the same settings, a self-signed SSL cert and an Exchange server. The Exchange server's webmail.xxxx.xxx address is supplied to the iPhone along with the SSL cert in a mobileconfig file.

Does anyone have any insight on what may be causing our issues? This is very frustrating and we were really holding our breath hoping that 3.1 would fix the issue.