The mobile site has used a wildcard certificate for the last two years; Did
you recently begin experiencing this issue or was your code working in the
past?

-j


On Thu, Jul 22, 2010 at 6:43 AM, bjcoredev <jme...@gmail.com> wrote:

> It seems that SUN WTK 2.5.2 doesn't accept wildcard certificates
> I hope that mobile platforms accept wildcard SSL certificates. If this
> not the case, it will make twitter xAuth/oAuth unusable....
>
> Regards
>
>
> On 22 juil, 14:57, bjcoredev <jme...@gmail.com> wrote:
> > Hi
> >
> > My mobile app logged to twitter using xAuth and was working like a
> > charm until the last SSL certicate changed
> > (seehttp://
> groups.google.com/group/twitter-development-talk/browse_thread...)
> >
> > My app logs correctly with the new certicate on real device (N97)  but
> > failed with the 2.5.2 Sun Wireless Toolkit wich i use to develop my
> > app.
> >
> > when i request token with the url (with all the parameters needed):
> https://api.twitter.com/oauth/access_token
> >
> > I get the following error message relative to the SSL certificate:
> >
> > Subject alternative name did not match site name
> >
> > It seems that the SSSL certificate doesn't match the host name
> > (api.twitter.com)
> >
> > I can't now no longer code end test my app on the computer
> > Help !!!
> >
> > I repeat: All was working fine before the SSL certificate change on
> > the 21/07/2001 1AM GMT.
> >
> > Regards
>

Reply via email to