[ngw] iOS 5 Safari and WebAccess

Danita Zanre dzanre.ngwlist at gmail.com
Fri Oct 21 01:59:25 UTC 2011 

That said, I've had no problems with WebAccess 8 or Ascot with iOS5.  So it must manifest itself differently depending on what you are doing.

Danita

On Oct 20, 2011, at 7:39 PM, Elbert LaGrew wrote:

> This is a known issue with Safari in IOS 5.  There is more information on the forums about it.  Opera will work fine.
> 
> --El
> 
>>>> Matt Weisberg  10/20/11 6:16 PM >>>
> 
> This sounds like some different issues going on.  The other issue described is an SSL/TLS related with Safari.  Are you having that issue too?  I've tested 8.0.2 HP3 on Linux direct from iPhones, iPods, and IPads all using IOS5 and they all work fine.  This is Apache on Linux with certs from commercial vendors (Verisign, Go Daddy, RapidSSL) and all work just fine.  So you might want to at least look at getting on the latest GW code.
> 
> Same with IMAP.  All devices with IOS5 I've tested work, but I'm testing all with 8.0.2 HP2 and HP3. And this is IMAP over SSL, again all with commercial certs.  
> 
> So I'd start there, getting onto current code, and then look at the PO logs and see what is really happening with the IMAP connections.  
> 
> Matt
> 
> On Oct 20, 2011, at 5:03 PM, Denny Brahce wrote:
> 
>> We have GroupWise/WebAccess 8.0.1 on NetWare 6.5.8.  We have the same
>> problem with all the iPads and iPhones that were working 3 weeks ago.  They
>> suddenly stopped working.  We were using IMAP (without SSL) with the phones
>> and they, too stopped working.  I have made NO changes to GroupWise or the
>> servers in any way.  ALL other devices continue to work.  I have no iChain.
>> 
>> Desperately looking for a fix.  Everyone wants to know what "I" broke.  I
>> believe it's an Apple IOS problem.  I had an Apple sales rep talk to an
>> Apple tech who was supposed to get back to me, but so far I have not heard
>> anything.
>> 
>> The iPads can browse to the IMAP server by name and it resolves to the
>> correct IP address without a problem.  They just won't "Talk" to it.  The
>> iPhones just say they are unable to talk to the IMAP server.  I'm convinced
>> the problem is with Apple and that I have the same root cause as what
>> started this entry into the NGWList.
>> 
>> Any help would be greatly appreciated.
>> 
>> Thanks,
>> Dennis Brahce
>> Flint, MI Schools
>> 
>> 
>> 
>> 
>> On Thu, Oct 20, 2011 at 12:27 PM, Matt Weisberg  wrote:
>> 
>>> 
>>> In a normal setup, iChain would be the SSL endpoint, not Apache on the Web
>>> Access server.  So all the TLS negotiation would happen there.  So I don't
>>> believe doing anything in Apache would help with this.
>>> 
>>> The last iChain patch was Support Pack 6 (2.3.418) which came out back in
>>> February of 2009.  I didn't see anything about TLS negotiation in the fix
>>> list for that patch.  The best would be to move to Access Manager.  Not a
>>> trivial undertaking, but a necessary one.  I'm still converting several
>>> customers off iChain myself.  There was a lot of it out there and it just
>>> worked, so it got left in place at many sites.
>>> 
>>> FWIW, Access Manager is a FAR superior product.
>>> 
>>> Matt
>>> 
>>> 
>>> On Oct 20, 2011, at 11:43 AM, Daniel Shelley wrote:
>>> 
>>>> I'm not 100% convinced that iChain is the guilty party in this case.  But
>>> maybe that just shows my lack of understanding of iChain.
>>>> 
>>>> Does iChain do all of the TLS negotiation, or does some of it get
>>> delegated to GroupWise WebAccess?  In other words, would an upgrade of the
>>> Apache server on the other side of iChain possibly help?
>>>> 
>>>> Daniel Shelley
>>>> Ghost Pattern Software
>>>> iPhone and Android apps for GroupWise
>>>> 
>>>> 
>>>> On Thu, Oct 20, 2011 at 9:26 AM, Matt Weisberg 
>>> wrote:
>>>> iChain hasn't been supported now for quite a long time (Access Manager is
>>> the replacement), so there will be no patches for that.  I did just test GW
>>> Web Access behind Access Manager using IOS 5 and that works just fine.
>>>> 
>>>> Matt
>>>> 
>>>> -----
>>>> Matt Weisberg
>>>> Weisberg Consulting, Inc.
>>>> matt at weisberg.net
>>>> www.weisberg.net
>>>> ofc. 248.685.1970
>>>> cell 248.705.1950
>>>> fax 248.769.5963
>>>> 
>>>> 
>>>>>>> Daniel Shelley  10/20/11 10:49 AM >>>
>>>> Dan,
>>>> 
>>>> We are seeing this same issue with a small number of our customers. The
>>>> issue does affect our iPhone apps too. In fact, we have had a number of
>>>> emails from your users.
>>>> 
>>>> We found the same technical note that you did. I do believe this is the
>>>> problem.
>>>> 
>>> http://developer.apple.com/library/ios/#technotes/tn2287/_index.html#//apple_ref/doc/uid/DTS40011309
>>>> 
>>>> We went through this same sort of thing last year with SSLv3 vs TLS and
>>>> NetWare 6.5 sp6. Eventually last year Apple provided a way to turn off
>>>> forcing TLS through their iPCU MDM tool.
>>>> 
>>>> I guess that there is no patch for iChain that might fix this? Maybe an
>>>> unapplied service pack? That would be to easy.
>>>> 
>>>> I am VERY interested to know if you figure out a solution.
>>>> 
>>>> Thanks,
>>>> Daniel Shelley
>>>> Ghost Pattern Software
>>>> iPhone and Android apps for GroupWise
>>>> 
>>>> 
>>>> On Thu, Oct 20, 2011 at 7:49 AM, Daniel Hunt  wrote:
>>>> 
>>>>> Interesting.  We are using iChain in front of our WebAccess gateway.
>>> It is
>>>>> apparently iChain in combination with the way that iOS 5 implements TLS
>>> that
>>>>> is the issue.  Apparently iChain is not "...downgrading gracefully to a
>>>>> supported protocol version."
>>>>> 
>>>>> Here is a relevant forum message that also links to Apple's own doc on
>>>>> changes in TLS.
>>>>> 
>>>>> 
>>>>> 
>>> http://forums.novell.com/novell/novell-product-discussion-forums/groupwise/groupwise-8x/gw8-clients/447056-webaccess-ios5.html
>>>>> 
>>>>> And here is the link to Apple's doc:
>>>>> 
>>>>> 
>>>>> 
>>> http://developer.apple.com/library/ios/#technotes/tn2287/_index.html#//apple_ref/doc/uid/DTS40011309
>>>>> 
>>>>> So Joshua, that helps to know that the WebAccess gateways themselves
>>> (or I
>>>>> guess the Web server part of them) are not the issue.  Are you using
>>> Apache
>>>>> or IIS for the Web server part of WebAccess?
>>>>> 
>>>>> dan
>>>>> 
>>>>> 
>>>>> 
>>>>>>>> "JOSHUA PITLICK"  10/20/2011 8:29 AM >>>
>>>>> I just successfully logged in to both our GW7 WebAccess and GW8
>>> WebAccess
>>>>> using my iPhone 4 with iOS 5.  I have not changed any of the Safari
>>> settings
>>>>> on my phone.
>>>>> 
>>>>> 
>>>>> Joshua Pitlick
>>>>> Contractor, AAC Inc.
>>>>> Office of Information Technology
>>>>> U.S. Equal Employment Opportunity Commission
>>>>> 
>>>>> 
>>>>>>>> "Daniel Hunt"  10/20/2011 8:01 AM >>>
>>>>> We are having a problem with iPhones or iPads after they have been
>>> upgraded
>>>>> to iOS 5.  After doing that the user can't browse to a GroupWise
>>> WebAccess
>>>>> gateway.  What happens is that the brower session just times out.  We
>>> are
>>>>> using WebAccess 7 at this point.  Has anyone else seen this?  Does it
>>> work
>>>>> with WebAccess 8?  Is there some setting in Safari that has to be
>>> changed?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Dan
>>>>> 
>>>>> 
>>>>> The information contained in this electronic mail transmission is
>>> intended
>>>>> only for the use of the recipient(s) named above.  It may contain
>>>>> proprietary, confidential or privileged information of the sender.  If
>>> you
>>>>> are not the intended recipient, you are hereby notified that any
>>> disclosure,
>>>>> dissemination, distribution or copying of the information contained in
>>> this
>>>>> transmission is strictly prohibited.  If you have received this
>>> transmission
>>>>> in error, please notify the sender immediately by reply electronic mail
>>> and
>>>>> delete the original message and any copy of it from your computer
>>> system..
>>>>> _______________________________________________
>>>>> ngw mailing list
>>>>> ngw at ngwlist.com
>>>>> http://ngwlist.com/mailman/listinfo/ngw
>>>>> _______________________________________________
>>>>> ngw mailing list
>>>>> ngw at ngwlist.com
>>>>> http://ngwlist.com/mailman/listinfo/ngw
>>>>> 
>>>>> 
>>>>> The information contained in this electronic mail transmission is
>>> intended
>>>>> only for the use of the recipient(s) named above.  It may contain
>>>>> proprietary, confidential or privileged information of the sender.  If
>>> you
>>>>> are not the intended recipient, you are hereby notified that any
>>> disclosure,
>>>>> dissemination, distribution or copying of the information contained in
>>> this
>>>>> transmission is strictly prohibited.  If you have received this
>>> transmission
>>>>> in error, please notify the sender immediately by reply electronic mail
>>> and
>>>>> delete the original message and any copy of it from your computer
>>> system..
>>>>> _______________________________________________
>>>>> ngw mailing list
>>>>> ngw at ngwlist.com
>>>>> http://ngwlist.com/mailman/listinfo/ngw
>>>>> 
>>>> _______________________________________________
>>>> ngw mailing list
>>>> ngw at ngwlist.com
>>>> http://ngwlist.com/mailman/listinfo/ngw
>>>> 
>>>> 
>>> 
>>> --------
>>> Matt Weisberg
>>> Weisberg Consulting, Inc.
>>> matt at weisberg.net
>>> www.weisberg.net
>>> ofc. 248.685.1970
>>> cell 248.705.1950
>>> fax 248.769.5963
>>> 
>>> _______________________________________________
>>> ngw mailing list
>>> ngw at ngwlist.com
>>> http://ngwlist.com/mailman/listinfo/ngw
>>> 
>> _______________________________________________
>> ngw mailing list
>> ngw at ngwlist.com
>> http://ngwlist.com/mailman/listinfo/ngw
> 
> --------
> Matt Weisberg
> Weisberg Consulting, Inc.
> matt at weisberg.net
> www.weisberg.net
> ofc. 248.685.1970
> cell 248.705.1950
> fax 248.769.5963
> 
> _______________________________________________
> ngw mailing list
> ngw at ngwlist.com
> http://ngwlist.com/mailman/listinfo/ngw
> 
> _______________________________________________
> ngw mailing list
> ngw at ngwlist.com
> http://ngwlist.com/mailman/listinfo/ngw

More information about the ngw mailing list