Hi Everybody,
Now, I need to implement SSO for my project. My project's env is
JBoss. window2003 AP. My problem is I have no idea how to do SSO for
my project. I checked it on internet. someone said it need use some
production what can support SSO, like weblogic. but I am not sure it's
best and simple way.
Any idea?
Thank u in advance.
Joey
M.J. Dance - 12 Oct 2006 11:54 GMT
> Hi Everybody,
>
> Now, I need to implement SSO for my project. My project's env is
> JBoss. window2003 AP. My problem is I have no idea how to do SSO for
> my project. I checked it on internet.
Try here: http://justfuckinggoogleit.com/search?q=single+sign-on
Or here: http://www.google.com/search?q=define:single+sign-on
Or here: http://en.wikipedia.org/wiki/Single_sign-on (make sure you "check" all
of the See also stuff)
> someone said it need use some
> production what can support SSO, like weblogic. but I am not sure it's
[quoted text clipped - 4 lines]
>
> Joey
impaler - 12 Oct 2006 12:16 GMT
> Hi Everybody,
Hi
> Now, I need to implement SSO for my project. My project's env is
> JBoss. window2003 AP.
> My problem is I have no idea how to do SSO for
> my project. I checked it on internet. someone said it need use some
> production what can support SSO, like weblogic. but I am not sure it's
> best and simple way.
There are lots of SSO framworks and utilities out there.
You can just google sso java and get a lot of info.
However I currently use RSA Cleartrust but the basic idea of a SSO is
simple.
If you use a common repository for your apps then create a token in the
logon app and persist it in the shared repository or in a cookie and
validate it in the other apps and should contain info that will be used
to rebuild the session from it. Usually username should be enough. Bear
in mind that sensitive information should be encrypted.
also can have a look at: http://www.josso.org/
You can use filters for servlets, ore include de token verification
declaratively into your application security
Regards
Brandon McCombs - 13 Oct 2006 04:44 GMT
> Hi Everybody,
>
[quoted text clipped - 8 lines]
>
> Joey
If you can tie into IE with your app then you can take advantage of the
ability for IE to integrate with Windows authentication and therefore
utilize cached credentials on an XP client workstation (if it is joined
to a Windows 2003 domain and it sounds like it would be in your case).
This would alleviate the need for a user to have to input a username and
password to access your app but they still get authenticated simply by
having a Windows domain account.
Joey - 17 Oct 2006 10:08 GMT
Hi Brandon.
Of course, My customer is using Win2003 Domain and XP Client. your
solution seems to be what I need. But, could u please give me more
information. like, Do I need to use Active Directory or something like
this.
Thanks.
Joey
> > Hi Everybody,
> >
[quoted text clipped - 16 lines]
> password to access your app but they still get authenticated simply by
> having a Windows domain account.