Thanks for the reply<br>But I am not sure I understood your suggestion about cookies entirely.<br>How would the administrator enable the cookie for users accounts?<br>I mean how do I save the cookies from session of one application and use it for the other?<br>
<br>Sorry if this is a stupid question, I am only a beginner.<br><br>Thanks<br>Malveeka<br><br><br><br><div class="gmail_quote">On Tue, Jun 9, 2009 at 4:47 AM, SitG Admin <span dir="ltr"><<a href="mailto:sysadmin@shadowsinthegarden.com">sysadmin@shadowsinthegarden.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The reason we want to implement OpenID Provider for Mailman is so that we can use the single sign on for our other internal accounts like our internal wiki etc.<br>
We want our users to login in just their mailman account and have single sign on for their other accounts.<br>
</blockquote>
<br></div>
If you're getting deep enough into the Mailman code and wiki code to patch their existing login systems with OpenID, you should be able to rig something much simpler with, say, just a cookie. This might lead to security problems if you're hosting each service on a different subdomain (with cookies delivered to *.<a href="http://domain.com" target="_blank">domain.com</a>) AND users get their own webspace on subdomains (since then users could read session cookies from other users), but if all the subdomains are official you should be fine :)<br>
<br>
-Shade<br>
</blockquote></div><br>