How is this different from OAuth?
With OAuth, you can authenticate a user at an external server and get access to their profile info. However you aren't sharing a session.
A user logs in to website foo.com using Google OAuth. Next he visits website bar.org which also uses Google OAuth. Regardless of that, he is still required to press on the 'login' button on bar.org.
With Jasny/SSO both websites use the same session. So when the user visits bar.org, he's automatically logged in. When he logs out (on either of the sites), he's logged out for both.
https://github.com/jasny/sso
http://stackoverflow.com/questions/5062569/how-to-do-single-sign-on-with-php
Why SSO account (company gmail) cant use as SSMTP sender ?
If you're just interested in reading the emails in a Gmail inbox you should forgo the cURL pseudo-browser path; instead, enable POP or IMAP on the Gmail account and use PHP's excellent IMAP/POP3 functions to access the Gmail inbox.
If on the other hand you're trying to create some sort of single-sign-on service you're straight out of luck. Why is this? Well, even if your server manages to authenticate and persist cookies from Gmail, you have no way of storing these Gmail cookies in the client's browser. Only requests that originate from mail.google.com can set Gmail cookies. This is known as Same origin policy.
http://stackoverflow.com/questions/4061537/best-way-to-implement-single-sign-on-with-all-major-providers
With OAuth, you can authenticate a user at an external server and get access to their profile info. However you aren't sharing a session.
A user logs in to website foo.com using Google OAuth. Next he visits website bar.org which also uses Google OAuth. Regardless of that, he is still required to press on the 'login' button on bar.org.
With Jasny/SSO both websites use the same session. So when the user visits bar.org, he's automatically logged in. When he logs out (on either of the sites), he's logged out for both.
https://github.com/jasny/sso
http://stackoverflow.com/questions/5062569/how-to-do-single-sign-on-with-php
Why SSO account (company gmail) cant use as SSMTP sender ?
If you're just interested in reading the emails in a Gmail inbox you should forgo the cURL pseudo-browser path; instead, enable POP or IMAP on the Gmail account and use PHP's excellent IMAP/POP3 functions to access the Gmail inbox.
If on the other hand you're trying to create some sort of single-sign-on service you're straight out of luck. Why is this? Well, even if your server manages to authenticate and persist cookies from Gmail, you have no way of storing these Gmail cookies in the client's browser. Only requests that originate from mail.google.com can set Gmail cookies. This is known as Same origin policy.
http://stackoverflow.com/questions/4061537/best-way-to-implement-single-sign-on-with-all-major-providers
Comments
Post a Comment