I've been experimenting with the different options for connecting to
Analysis Server.
At one point I selected "Credentials stored securely in the report
server" and put in a User Name ("dummyUser") and a Password.
Then I decided to try "Credentials are not required". When I did
this, the report still worked. I looked in Profiler, and saw that
dummyUser was still there as the NTUserName.
So I thought that maybe the connection was cached, and went home for
the weekend. But I try it this morning and it still works the same
way.
Any ideas about what's happening?On Aug 28, 8:55 am, cowznofsky <jhco...@.yahoo.com> wrote:
> I've been experimenting with the different options for connecting to
> Analysis Server.
> At one point I selected "Credentials stored securely in the report
> server" and put in a User Name ("dummyUser") and a Password.
> Then I decided to try "Credentials are not required". When I did
> this, the report still worked. I looked in Profiler, and saw that
> dummyUser was still there as the NTUserName.
> So I thought that maybe the connection was cached, and went home for
> the weekend. But I try it this morning and it still works the same
> way.
> Any ideas about what's happening?
This definitely looks like a bug, since if I try a new datasource and
use "Credentials are not required" it fails, as expected. But once a
valid User Name has been used, and then the option is switched back to
"Credentials are not required", it still works.
Wednesday, March 7, 2012
AS credentials confusion
Labels:
analysis,
confusion,
connecting,
credentials,
database,
experimenting,
microsoft,
mysql,
oracle,
point,
securely,
selected,
server,
sql,
stored
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment