Windows Authentication and Data Stores

[Former Member]

Hi,

We have a sql server system in an other division of our company we need to get data from.

The people who run that system are insistent that windows authentication is all they support. This is causing us issues.

Even though our data services processes are running under the relevant windows (AD) account, when I try to create a data store with windows authentication, it seems to be using my credentials (i.e. the designer's) rather than the server processes.

I tried to run the designer under that account, but got a licence issue..

Has anyone else experienced this ? Did you solve it ? I've found similar questions in the furum but not with a solution.

Thank you.

[Former Member]

Hello

Using Windows authentication will work fine with Data Services.  As Peter correctly states, the server user and your local user will both require to be added as SQL Server users.  If this is a problem and your server is on Windows, it is possible to run the Designer on the server and create the datastore and import the metadata from there.  Although you will not be able to access any data through the Designer.

Michael

[Former Member]

I had bad experience with Windows authentication and finally switched to SQL server authentication by creating a user account in SQL and logging in.

Arun

[Former Member]

Hi,

Windows authentication could not be used while your connecting the datastore with SQL Server. only SQL server authentication with its own credentials is possible to set up a data store. Windows authentication will lead you to your own OS credentials which would not been provided an access to SQL Server,

Regards,

Raji

[peter_houston]

The BusinessObjects Data Services service user is used when executing jobs, not when developing in the Designer.  The Designer uses the local user account. 

To setup the datastore, you need to launch the Designer with a user that can access the database, as you tried to do.  The licensing issue you ran into sounds like a UAC issue. 

I would recommend that you try running the Data Services License Manager as administrator and readd your keycode. You can do this by right click on the License Manager shortcut and select “run as administrator”.

The other option would be to have the dba grant your AD user account rights to access the database for Designer development.  You will then be able to create the datastore and design your jobs in the Designer.  Job execution will still use the BusinessObjects Data Services service AD account.

Regards,

Pete Houston

[Former Member]

If you use windows authentication while you configure the datastore, it will use the windows user of the OS that you are in. If the other SQL Server only uses windows authentication, logging into that database seems to be possible only from within that OS. A SQL Server authentication would be required in this case, if you want to access that database from outside.

Regards,

Suneer