GWT InvocationException with Siteminder's embedded SMPostPreserve INPUT tag

582 views
Skip to first unread message

JohnnyGWT

unread,
Oct 5, 2009, 8:11:23 PM10/5/09
to Google Web Toolkit
Any info/hints on this situation would be greatly appreciated.

We have a GWT UI making GWT RPC calls to a db for data. It also opens
COGNOS reports within GWT Frames.
We're using CA Siteminder Web Agent for single sign on that forwards
requests to a Web application server if the user is verified.

GWT RPC calls work fine with the user first starts up a new IE
browser.
** After a user opens a single COGNOS report (displayed within a GWT
Frame), every subsequent GWT RPC call is blocked by the SiteMinder Web
Agent and returns as a GWT InvocationException.

The only contents of the GWT InvocationException is the following:

<HTML><HEAD><TITLE></TITLE></HEAD><BODY
onLoad="document.AUTOSUBMIT.submit();">This page is used to hold your
data while you are being authorized for your request.<BR><BR>You will
be forwarded to continue the authorization process. If this does not
happen automatically, please click the Continue button below.<FORM
NAME="AUTOSUBMIT" METHOD="POST" ACTION="http://logon-
dev.worldnet.ml.com/siteminderagent/ntlm/creds.ntc?
CHALLENGE=&SMAGENTNAME=-SM-LgQm3VreLhAyRKAPopfj8NRmegg
%2bQIxSkzBfsID33rwfXbkiqQvmVi8FPHiXUCSr&TARGET=-SM-http%3a%2f%2ftoro--
dev%2elvt%2eus%2eml%2ecom%2fTOROWeb%2ffx"><INPUT TYPE="HIDDEN"
NAME="SMPostPreserve" VALUE="cbYiaOEFLV/LEH6Ltz7XyoSlHRPfbxrou8Q/
GWbcBKFbcTURbi9nWtgvwa75e7ITSApqeHNIbUfQ4OZGs1RMqP/zxE3d
+W1A8krkfzcTGfeZf5IUfdA48it3k9HjM9AeRNGqTri05RG4w6Xp4hc4kNN8VMBEzUBHYWYs6JaHbd71mgohhfnXbwMFNWcmHSnDjZyT/
nCzqk8tRPh3+IVqFeQNcEb/+JCbwdhz233wXpfwtGCyjo5wEqP9pxjZQIvz"><INPUT
TYPE="SUBMIT" VALUE="Continue"></FORM></BODY></HTML>

As soon as you refresh the browser, GWT RPC calls work again (get
passed SiteMinder), until a COGNOS report is opened

I've seen a few URL's regarding this embedded HTML page, but nothing
with regards to GWT or how to get around it.

Yes, this involves SiteMinder (and GWT), BUT before you say its posted
in the wrong discussion group, its causing issues with GWT code, so
this group is appropriate.

If anyone has any ideas on how to get around this I'd really
appreciate it.

Thanx in Advance,

Nathan Wells

unread,
Oct 6, 2009, 6:31:56 AM10/6/09
to Google Web Toolkit
It might help if you posted some sample code, but from what I
understand you are doing something like -

//user clicked on some control, open cognos report.
Frame cognosReport = new Frame(cognosUrl);
RootPanel.get("frameContainer").add(cognosReport);

Is this accurate? Is this where you're seeing the error? Technically,
this shouldn't be making a gwt-rpc call, so I'm guessing that I'm just
not understanding where your error is occurring. Again, some sample
code would help.

JohnnyGWT

unread,
Oct 6, 2009, 10:32:10 AM10/6/09
to Google Web Toolkit
Thanks for responding. I do open a cognos report in the fashion you
displyed. It is not making a gwtrpc call.
My issue is that subsequent gwtrpc calls to our database (for non-
report info) are blocked by Siteminder and return as an
invocationexception. Our gwtrpc calls work fine until we open a cognos
report. After that, they are blocked and we get the
invocationexception with the smpostpreserve HTML.

Nathan Wells

unread,
Oct 6, 2009, 11:15:02 AM10/6/09
to google-we...@googlegroups.com
I think I understand your issue now. Like you said in your first post, this is probably a siteminder configuration problem... Not exactly sure how to work around it, but it would probably involve dealing with the InvocationException in your AsyncCallback (assuming that's what's coming through in the onFailure). You might try building a request and sending it to the url returned in the ACTION attribute below, and adding the parameters in the hidden field. However, that's just a guess.

My bet is that you will probably spend more time trying to work around the issue than just fixing SiteMinder's configuration.

HTH
Nathan Wells

Daniel Jue

unread,
Oct 6, 2009, 2:27:09 PM10/6/09
to google-we...@googlegroups.com
Just throwing this out there:

I used to get that waiting page when I accidentally had an application
switching between https and http.

Daniel Jue

unread,
Oct 6, 2009, 2:31:08 PM10/6/09
to google-we...@googlegroups.com
I meant to mention that my problem did not involve GWT (I wasn't using
it at the time) nor my other UI framework, Tapestry. I just had some
links being generated as http from development that needed to be https
in staging.
Reply all
Reply to author
Forward
0 new messages