How did your testing go? I compared SSO Webcontent (which works, sort of) to SSO IFrame classes and I see a method for preemptive login in the webcontent class but no reference at all in the SSO IFrame class. Does this just mean it is being done differently, or is something amiss in the SSO IFrame class?
From: David Sean Taylor <[email protected]> To: Jetspeed Users List <[email protected]> Date: 08/11/2010 05:21 PM Subject: Re: SSO IFrame form authentication I'm out of office today- I will test form auth tomorrow, make sure it's not completely broken in 2.2.1 - it should at least be posting, one obvious problem could be user specific prefs overriding defaults.. Sent from my pretentious iPhone On Aug 11, 2010, at 9:58 AM, [email protected] wrote: > I have perused that doc many times. I have placed SSI IFrame on a page. I > then went to Admin->PAM pages to set properties for the SSO IFrame > portlet. I have configured the following parms. > > sso.type form > sso.form.Principal user > sso.form.Credential password > sso.form.Action http://webb2c1/Login.htm > > Set in the edit preferences dialog > SRC http://webb2c1/mywebapp/Customers.htm > SSO Principal mballard (my id on the remote webapp) > SSO Credential xxxxxxx (my password on the remote webapp) > > I have also set this up or verified this in the sso-admin portlet. > > Once I set all this up, I log out and back in, then go to my SSO IFrame > page and I get the login screen for the remote app. I have traced this > with Wireshark and all I see is the GET for the SRC url, then a 301 > redirect to the login page. I see no attempt to ever post the login.htm > with the login form. > > Again, I have googled for two days to figure out what I'm doing wrong, but > I do not see it how to make it preemptively send my login before accessing > SRC url. > > > > > > From: > David Sean Taylor <[email protected]> > To: > Jetspeed Users List <[email protected]> > Date: > 08/11/2010 10:57 AM > Subject: > Re: SSO IFrame form authentication > > > > On Wed, Aug 11, 2010 at 6:37 AM, <[email protected]> wrote: >> I am attempting to use SSO IFrame in Jetspeed 2.2.1 with no success. I >> feel like I get the concept and have configured to authenticate to an >> internal webapp using simple form based posting, however, when I access >> the site via the SSO IFrame portlet, the authentication process never >> seems to be invoked. I instead see the login page for the remote site. > I >> have traced the flow via Wireshark and see no evidence that the IFrame >> ever attempts to post the form url. I have tried several internal sites >> with similiar results. What am I missing? >> > The SSO IFrame and Web Content portlets are configured with a set of > preferences. The documentation for these preferences is found here: > > http://portals.apache.org/jetspeed-2/deployguide/config-sso.html > > I would start there, and make sure the preferences are set correctly > for your IFrame portlets. As the administrative user, you should be > able to set these preferences in Edit Defaults mode for all users. > Form based authentication is one of the preferences options, make sure > it is set (sso.type=form) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean (mailgw2:E817D1E6FC.705AC). > > > > > This communication and any attachments are confidential, protected by > Communications Privacy Act 18 USCS § 2510, solely for the use of the > intended recipient, and may contain legally privileged material. If you > are not the intended recipient, please return or destroy it immediately. > Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean (mailgw2:1D77C1E6FE.658BA). This communication and any attachments are confidential, protected by Communications Privacy Act 18 USCS § 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you.
