We have renewed the existing wildcard certificate and will be deploying it
soon to api.twitter.com and oauth.twitter.com.
It's from the same vendor, so there should be no issues.
On Fri, Jul 16, 2010 at 11:26 AM, Carlos <carlosju...@gmail.com> wrote:
> After getting SSL errors on Windows Mobile 6.0 with connections to
> api.twitter.com due to that OS not having that cert installed, I
> started up firefox and connected to https://api.twitter.com and
> noticed this <see screenshot>
> It's listed as expiring on 7/27/2010. I'm sure that twitter is aware
> of this and planning a cert change but since it's less than 2 weeks
> away I thought I'd bring it up just in case.
> Also, will the new cert be trusted by default on most current mobile