First of all, please keep in mind that in this post by "Single Sign On" (SSO) I intend something like Microsoft's ".NET Passport" ("one name, one password" for every web service whatever the domainname would be) and not the meaning used by some of US universities (one name, one password for every application inside .domainname.com).

This weekend I did some online research on "single sign on" (SSO) trying to determine the pros and cons of this "technology" and eventually gathering information about such providers and even software on the market.
The main keyword in this study was (of course) "perl" :)

The "pros and cons" issue it's already a too hairy discussion so I will step over it (for now) and offer just some links for the interested ones:

First thought was to find a provider for such services and just use it (counting on the fact they offer a perl API). OK, Google eased my way and found out that every(?) such provider would be OK for me.
But as I really doubt my client would go for it (using a "remote service" for such a sensitive service) I went farther and searched for products that would be deployable on client's site. OK, I found out some, but all(?) require Java technology (at least on the server side), thing that I clearly want to avoid.

The final solution would be to implement out own home brewed SSO system... and here comes the question - a request for comments in fact from the fellow monks that maybe already did this (or are planning to do it).

Here are some points I'd like to hear more from you:

(Of course, opinions on the "pros and cons" issue - and maybe alternative systems(?!) - are welcome too :)
Thanks In Advance for all the feedback.

PS: I didn't give any commercial links here because I did not want to use this space for advertising, Google's AdSense does it very well :)

UPDATE: at arden's suggestion I minimized the usage of abbreviations/acronyms. Adding abbr (or acronym) statements for each such occurence was not possible as these tags are not allowed :(

UPDATE2: added readmore tags

--
AltBlue.

In reply to "Single Sign On" perl based solutions? by AltBlue

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.