Single Sign On - How To Implement It?

4 replies
Hi Warriors,

Need your advice on implementing single sign on (SSO).

Say I've a couple of portals with the following platforms :

- Joomla CMS
- phpBB forum
- Moodle
etc.

How can I integrate them together with single-sign-on feature. Meaning, a single log in ie. say at the Joomla site, will enable the users to roam and access the other portals.

An example is the Google sites. Single log in to access Gmail, Google Documents, AdSense account etc.

What is the cost and technicality for implementing SSO?

Thanks!
#implement #sign #single
  • Profile picture of the author GarrieWilson
    Two methods (off the top of my head):

    1: Recode all the sites to use one login.
    2: Write a PHP script that logs them in in the background.

    Cost would vary by the scripts and programmer.
    Signature
    Screw You, NameCheap!
    $1 Off NameSilo Domain Coupons:

    SAVEABUCKDOMAINS & DOLLARDOMAINSAVINGS
    {{ DiscussionBoard.errors[455431].message }}
  • Profile picture of the author Eric X Vignola
    you could also try and use some kind of tracking like a cookie for login information that all your sites look for. once they login on one site the cookie is placed and if they go to another site the cookie will log them in automatically
    Signature

    Need Articles, Reports, eBooks, anything?
    Check Out My Ghost Writing Services

    PLR articles and reports? Coming Soon...

    {{ DiscussionBoard.errors[455574].message }}
  • Profile picture of the author Andy Fletcher
    Single Sign On is very complicated and likely very expensive so think carefully before you explore this option.

    You will need to create your own user account system, which someone signing up to any of the services (or who is already signed up) gets an account on.

    Each platform that you have a site built on (Joomla/Moodle etc) will need to have a new authorization mechanism created for it that contacts the central account store rather than using its own.

    Those parts will get you as far as federated sign on. That's to say that have a central account will allow them to login to all of your sites but the login won't be carried across so they'll need to login at each site individually.

    To get as far as a fully Google-esque SSO your login pages will need to be able to check if someone is already signed into the main system and redirect accordingly. (That's what's happening when you go to sign into a Google service when you're already logged in somewhere else and it says "loading" and redirects you).

    SSO gets even more complicated still when you have to deal with permissions/access to the different sites. Eg instead of having a very open Google like setup where you just need an account and you can use everything you have a set of sites that require payment to access them, with payment only gaining you access to one site. To do that your central account/authorisation system needs to be even more complicated and hooked up to your payment processor so it can track which sites they can login to.

    Don't wish to be a doom monger but just want to make sure you appreciate the scope of what you're looking to do here.

    Cheers,

    Andy
    {{ DiscussionBoard.errors[455584].message }}
  • Profile picture of the author williamtan
    I've touched on the topic of SSO a couple of years back and the conclusion then is successful SSO implementation are for those big companies like Google and Yahoo. It seems virtually impossible for the small-medium dotcom to achieve SSO.

    Until now, SSO seems to be technically tough as very few, without deep corporate pocket, are close to successful implementation.
    {{ DiscussionBoard.errors[456069].message }}

Trending Topics