You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by chocba <ch...@gmail.com> on 2009/10/06 22:12:05 UTC
Links and JetSpeed SSO
I've used the SSO webcontent portlet, in jetspeed 2.2, which was able to
login and render nytimes.com page in portlet. Instead, I would like to have
a link in my own portlet, say "http;//www.nytimes.com". If user click the
link, a new window has to open, automatically logged in to nytimes.com,
using the credential from jetspeed sso store. I've setup the url and
credentials using SSO Site Browser portlet. Can anyone please let me know
how to achieve this or what api need to be used? Thanks in advance.
--
View this message in context: http://www.nabble.com/Links-and-JetSpeed-SSO-tp25775770p25775770.html
Sent from the Jetspeed - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Links and JetSpeed SSO
Posted by David Sean Taylor <d....@onehippo.com>.
On Oct 23, 2009, at 11:46 AM, chocba wrote:
>
> Thanks David. I've one more question. The SSOWebContent Portlet
> doesn't seem
> to work for all external sites. The site that require cookies fails to
> sign-on. For instance, I configured sites such as gmail,
> webmail(outlook),
> which doesn't login at all. The nytimes.com worked since it was a
> simple
> form post and no cookies are exchanged during the post. Please let
> me know
> if this an open issue. Thanks.
>
>
Each form-based SSO works a little differently. There are often
additional form parameters that need to be sent. Sometimes there is
Javascript involved, or tokens from HTTP headers. Jetspeed does
provide configuration for handling additional form parameters,
including tokens. However the Jetspeed SSO solution doesn't work in
every case. We are still actively developing in the trunk and adding
sites as we progress. We have recently authenticated against JIRA. I
think it would be interesting to try the major mail providers. If you
want to try that out yourself, or create a JIRA issue for it, we can
try to get to it before the next release.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Links and JetSpeed SSO
Posted by chocba <ch...@gmail.com>.
Thanks David. I've one more question. The SSOWebContent Portlet doesn't seem
to work for all external sites. The site that require cookies fails to
sign-on. For instance, I configured sites such as gmail, webmail(outlook),
which doesn't login at all. The nytimes.com worked since it was a simple
form post and no cookies are exchanged during the post. Please let me know
if this an open issue. Thanks.
David Sean Taylor-3 wrote:
>
>
> On Oct 6, 2009, at 1:12 PM, chocba wrote:
>
>>
>> I've used the SSO webcontent portlet, in jetspeed 2.2, which was
>> able to
>> login and render nytimes.com page in portlet. Instead, I would like
>> to have
>> a link in my own portlet, say "http;//www.nytimes.com". If user
>> click the
>> link, a new window has to open, automatically logged in to
>> nytimes.com,
>> using the credential from jetspeed sso store. I've setup the url and
>> credentials using SSO Site Browser portlet. Can anyone please let me
>> know
>> how to achieve this or what api need to be used? Thanks in advance.
>>
>
> We don't currently have support for this feature, but I think there
> are several solutions that will require some coding that come to mind:
>
> 1. adding new functionality to Jetspeed links to support proxying the
> content through the Jetspeed server (much like how we proxy content
> with IFrames and Web Content portlets in the trunk today)
> 2. instead of using links, using existing SSO IFrames, to navigate to
> the content. Implement a new feature to then "detach" the iframed
> window via a new action on the portlet decorator
> 3. a completely new feature: using hidden iframes to login users (will
> require https ) transparently upon clicking on a link
>
> Related to #2, we are looking into a new desktop maximize mode that
> would effectively give a window 'full maximization' meaning that it
> will take up the entire browser window, including removing headers.
> this is still under development though
>
>
> Suggest that you create a JIRA issue if you would like to see this new
> feature
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Links-and-JetSpeed-SSO-tp25775770p26031445.html
Sent from the Jetspeed - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Links and JetSpeed SSO
Posted by David Sean Taylor <d....@onehippo.com>.
On Oct 6, 2009, at 1:12 PM, chocba wrote:
>
> I've used the SSO webcontent portlet, in jetspeed 2.2, which was
> able to
> login and render nytimes.com page in portlet. Instead, I would like
> to have
> a link in my own portlet, say "http;//www.nytimes.com". If user
> click the
> link, a new window has to open, automatically logged in to
> nytimes.com,
> using the credential from jetspeed sso store. I've setup the url and
> credentials using SSO Site Browser portlet. Can anyone please let me
> know
> how to achieve this or what api need to be used? Thanks in advance.
>
We don't currently have support for this feature, but I think there
are several solutions that will require some coding that come to mind:
1. adding new functionality to Jetspeed links to support proxying the
content through the Jetspeed server (much like how we proxy content
with IFrames and Web Content portlets in the trunk today)
2. instead of using links, using existing SSO IFrames, to navigate to
the content. Implement a new feature to then "detach" the iframed
window via a new action on the portlet decorator
3. a completely new feature: using hidden iframes to login users (will
require https ) transparently upon clicking on a link
Related to #2, we are looking into a new desktop maximize mode that
would effectively give a window 'full maximization' meaning that it
will take up the entire browser window, including removing headers.
this is still under development though
Suggest that you create a JIRA issue if you would like to see this new
feature
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org