Implications of using embedded user in URL to access a report

[tbarker]

I was wondering if there are any implications or concerns to be aware of when using one generic user and password embedded in the URL to access a report.  Such as, if multiple people are using the same URL to access the report and the report runs under that same generic user, is there any issues with how caching works.  Could one person potentially get results from what another person was running?  I am unfamiliar with how user caching works.  

[hozawa]

Shouldn't have any problem because each request will have a different session. I had one user who wanted this and haven't had any problem.

One problem with this approach is security. If the report contains information that filters by users, some users may be able to "guess" the username/password and get information.