How do I code a custom non-interactive authentication module to provide single sign-on between p

My environment has a total of four domains that link to one another. It is undesirable for the user to have to re-enter their user name and password each time they want to navigate to a new portal domain.

From what I have read, this will mean that multiple server sessions will be created as a result each time the user were to navigate to a new portal domain. This may be acceptable with a small user audience considering that the server sessions are set to a reasonable timeout value.

Having read through some of this forum I am lead to believe that this type of single sign on between portal domains is not supported or recommended.

Could coding a custom non-interactive authentication module provide this type of functionality? If this is still not recommended could someone please explain to me why? And finally, if someone could provide sample code or advice on how to implement this SSO between portals it would be appreciated greatly.

Thanks in advance,

[1000 byte] By [708937] at [2007-11-25 4:37:48]
# 1
The main problem you would run into when you do this would be that each domain would need to set its own cookie and this would conflict with the cookie set by the other domain.
Karthik_Krishnamoorthy at 2007-6-29 3:09:22 > top of Java-index,Web & Directory Servers,Portal Servers...