I have set up a dashboard and attached a domain and a focexec for a developer to test. Her user id has been assigned (and mine) to the dashboard. She first tested by going through our intranet, got the login page, logged in and then the dashboard popped up correctly but with another login overlaying it. This login stated 'invalid credentials for logging into the edaserver.' The only login id and password it would take is the one we use to sign on directly to the server.

when I went through MR and the BI intelligent dashboard, i got the same problem. This was not happening before and is not happening in production.

vegaskitkat,

Sounds like you have security turned on at the Reporting server where you didn't in the past. Is this a new install?

You have 2 'easy' options:

1. Set the Reporting Server to run with security "off" - not really recommended
2. Set the IBI_REPORT_USER and IBI_REPORT_PASS variables via the Admin console (Configuration - > Reporting Server)

The best option would be to set up Single Sign On, so that when you are logged in to Managed Reporting you are also logged into the Reporting Server. The Security manual will give you a better understanding of the ins and outs of authentication with WebFOCUS and all the components

Cheers

Stu

One other situation when I saw a similar problem was when the the report being executed was pointed to a different server instance than what the default server of the domain is.

We have setup different priority classes of Hi,Med&Low for the one EDA server we have on the mainframe. Priority reports are executed with the High priority class, with Low being our default.

If we had a report pointed to the 'High' server, and it was in a domain pointed to the default 'Low', we would get prompted to re-authenticate, even though these High & Lo pointers virtually are the same EDA server and re-authentication was not required. If the report execution server class and the domain default server classes are the same, this re-authentication required page does not pop-up.
You can validate this this looking at the "Properties" panel on the right-click menu.

Please review if you have a similar situation that could be causing your problem.

Sandeep Mamidenna

There is also the option of having the Dashboard/MRE/CUS Authenticate to the reporting server where MRE does not store the password just the id and the id matches an id that the reporting server can authenticate the user to.