We have a requirement to have reports inside of MRE (BI Dashboard), but provide the ability for them to be accessed from an external app. Furthermore, we have created HTML launch pages within MRE, which launch the reports. We are in a single-sign-on environment using COREid, so we're using MR_Drill to get into MRE. Here's the problem. If I link to a FEX directly, passing all the necessary MRE parameters, it works fine. However, if I link to my HTML launch page, passing the same parameters, it appears to not create the WebFOCUS cookie. The launch page fails when it tries to build the dropdowns (I think because the WF cookie wasn't created). I think one option would be to pull my launch page out of MRE, but would really like it to work as is, if possible. Any suggestions would be greatly appreciated.

This message has been edited. Last edited by: Jeff Elam,

There are probably a couple ways around this. Here's one suggestion: Instead of having and HTML launch page, per se, try creating a fex which has
-HTMLFORM BEGIN
your launch page html here
-HTMLFORM END

I haven't tried this because I don't know exactly how your pieces are interacting, but it may exhibit different behavior for a .fex instead of a .htm

Darin,
Excellent idea. Doesn't appear to act any differently, though. In any case, thanks for the suggestion.

Maybe executing some dummy code in your fex before the -HTMLFORM would set the cookie. Like
TABLE FILE CAR
SUM CAR
ON TABLE HOLD
END
-RUN
-HTMLFORM BEGIN
...

I think your MR_Drill is the problem here. If I understand it correctly, the MR_Drill will bypass security for the current request, that way a distributed report can still have active drill downs. I don't believe that the cookies are created when it is available. You will probably have to call the request without the MR_Drill, and all the other valid parms to get this working.

I'm about 85% confident that the above is correct. Maybe someone else here can confirm or deny it.

I tried taking out the MR_Drill parameter, and it now immediately prompts me to logon to Managed Reporting, which I don't want. This is the string I'm passing:

 https://server/ibi_apps/WFServlet?IBIMR_domain=oda4wgco...folder=#sampledsp249

Can you explain you SSO configuration in a nut shell?

OK. Using COREid (formerly Oblix). Users sign onto their application. A COREid cookie is created. Using HTTPS for the WebFOCUS app, but not for the other app. When the user links to the app or BI Dashboard (2 separate links), they don't need a passowrd, because they've already got the COREid cookie. MR_Drill is used to indicate who the user is to WebFOCUS.

Sorry Jeff ... my bad. It's the IBIMR_drill that is causing you problems.

Read this: This should help alot.

IBIMR_Drill is what we are using. I may have referred to it incorrectly above. If I take it out, I don't get into MRE at all. I had seen the posting you pointed to, and tried some of the techniques offered, but didn't find anything of specific use. Someone offered me this as a suggestion--is there javascript that can be called to create a WebFOCUS cookie?

Jeff,

How would your users normally log on? I assume that COREid is protecting the /ibi_apps end point, and adding either the IBIMR_Drill, or using some other header or cookie that then is linked to the MRE userid. I am not familiar with COREid, but I am with Siteminder, ClearTrust, and Entrusts SSO environments, and that is how all of them basically work.

Any light that you can share should help guide you to the appropriate URL that will both create the MR_COOKIE and call the appropriate html page (and subsequent report).