SQL connection with security for reports - data not returned properly

已答复 SQL connection with security for reports - data not returned properly

  • Tuesday, 18 September 2007 2:15 PM
     
     

     

    Hi,

     

    We're having some issues with reports securtiy.

    For example, a manager role is seeing data that he shouldn't.

     

    I'm wondering if didn't set up the connection string corrrectly.

    This is what i have currently.

    THanks for taking the time to have a look.

    Name:
    Description:
    Connection type:
    Connection string:
    Connection type:
    Connection string:
    Connect using:
    Display the following text to prompt user for a user name and password:
    User name:
    Password:

All Replies

  • Tuesday, 18 September 2007 5:19 PM
    Moderator
     
     Answered

    Hi Mike,

    You need to select "Windows Integrated Security" instead of "Credentials stored securely in the report server". Windows integrated security will use the credentials of currently login user and will show the correct data accordingly.

     

  • Tuesday, 18 September 2007 5:26 PM
     
     

    Thanks Umar.

     

    David Jennings replied with the same answer and i'll give you the same response i sent him.

     

    I initially thought that was how the connection should be done but one of the other developers changed it.

     

    The problem though now when it is set to integrated security, it gives a SQL connection error.

    I'm away from the office and don't know the exact error message they are getting.

    Maybe the users are not set up with report permissions?

     

    Thanks again.

  • Tuesday, 18 September 2007 5:46 PM
    Moderator
     
     

    Hi, Check out if connection string is right?

     

  • Tuesday, 18 September 2007 6:28 PM
     
     

    Yeah. Connection works.

     

    Right now i'm thinking if they've set up the user configuration correctly.

     

    The reason why i'm thinking about this is that some users can view certain reports.

     

    So...we'll have to figure out what those people did in setting it up.

     

    Thanks.