The main problem is that you need official SSL certificate for integration.

The way the 3.0 team was looking at doing it was having members store their facebook/WindowsLive login info in their vars file - not exactly what people mean by 'login using Facebook' (or maybe it is - I gave up on trying to get the OpenID thing to work).

Getting 'official' SSL certification IS a major hurdle and there have been moves by some major players to dump the current method of authentication. Curently only a few companies are 'authorized' to do it and not only does it require a large cash outlay if you have more than one site to worry about, the fact that they want things like your corporation identity number means that when you do see an 'authentic' SSL cert on a non-business site the owner has had to lie to get it. (http://lewayotte.com/2011/05/31/ssl-certificate-scam-yay-or-nay/)

(As an aside, real world research has shown that sites that show the 'TRUSTe' certification are more that twice as likely to be untrustworthy as sites that didn't bother.  )

(That said, it looks like at least a few Cert companies have lowered the price to some thing reasonable for hobby sites and I'll look at those later today.)

And another part of the problem is that there are few 'official' certifying organizations listed in the various browsers and email clients. So if your certification isn't listed with one of those few you may have spent big bucks for nothing.

So let's keep this one in mind once we have 2.6.2 squared away as this one will require quite a bit of research to do it well. (And as you guys should know by now, if I have more than 2 projects happening at once, they all get fubarred.  )

Quote:

to add Additionally, search engines have started giving preference to secure websites using HTTPS   

Quote:
hahaha we know and its not just you      :

Quote:

I hope to go on a bug hunt soon  so be prepared