Re: Is there a Login Portlet in Jetspeed 1.4?

[Glen Carl]

I have not seen a solid SSO standard specification. I like your idea of 
the properties file. We were just thinking of the properties file idea 
too, since we may have to support another SSO vendor for the deployment 
I am working with. However, we probably will not start this work until 
summer. I hope you can achieve a flexible Login portlet to handle the 
SSO interfaces.
Sorry to have missed your earlier emails. I have not looked to see how 
Jetspeed2 was addressing SSO, maybe some SSO interfaces are established 
in J2.
Good luck,
Glen

Jignesh Badani wrote:

Glen, when I meant an easier way, I meant an actual Login or SSO Portlet 
which would be available to Admins to customize and achieve SSO in a much 
simpler fashion . It could be even a properties file.

Choices available in the customizer could be: 
SSO Enable = yes/no
Name of HTTP Header/Cookie to trust = "http_some_header_variable"
Shared Secret (added security) = "secret"
Automatically Register user = yes/no
Default Role(s) = "user"
Default Group(s) = "HR"

Many portal solutions like Tibco. Plumtree provide this feature and makes 
sense too as Portal administrator need not go and hack into the code and 
change it in multiple places. And if more custom security is desired like 
secondary validation (if trusting HTTP header is not suffice), then the 
Portlet can be simply be extended.

Sounds like a good project for me. In the mean time, I have gone ahead and 
changed JLoginUser to read and trust the the HTTP header. I will now work 
on the Auto registration piece next.

Thanks for you help.
-Jignesh




Glen Carl <[EMAIL PROTECTED]>
03/17/2004 04:51 PM
Please respond to "Jetspeed Users List"
 
        To:     Jetspeed Users List <[EMAIL PROTECTED]>
        cc: 
        Subject:        Re: Is there a Login Portlet in Jetspeed 1.4?

The "Login portlet", is a portlet, but is a portlet for the operation of 
Jetspeed. The source code I mentioned is a component of this portlet. 
The "vm" login template is just the front end that will be replaced by 
your SSO tool. Just modifying the template probably will not work, and 
is not a wise design choice.
Glen

Jignesh Badani wrote:


Thanks Glen for your prompt response.

If you please read my earlier post : 
http://www.mail-archive.com/jetspeed-user%40jakarta.apache.org/msg11720.html

In there, I have mentioned that I tried going through the code you 
mentioned in your email. I was just hoping there was a better way. The 
text "Login portlet" in Resources.properties is misleading.

-Jignesh

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]