If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Different data source sign on by user/group

Started by mrl72, 16 Jul 2015 02:31:24 PM

Previous topic - Next topic

mrl72

Does anyone know if it's possible to have a data source use a different sign on for a user or group of users?

In our data source we have a sign on set for a DB service account. For some users we want when they create a report from the same package to use a different sign on.

Possible?

gpollock

We have something similar, where when you run a report, and it prompts to select from dev or production.  I tried looking up how we did it, but I can't find anything.  However, I see this how-to that might give you what you need.  Please follow-up on whether this works.

http://www-01.ibm.com/support/docview.wss?uid=swg21502986

bdbits

If you set up multiple connections within the data source, Cognos will have them choose which one. You should be able to preset the username/password on one connection, and prompt for the other. But as far as I know it is always going to ask which connection they want to use, so it might annoy your regular, service-account-based users.

MFGF

Quote from: bdbits on 16 Jul 2015 05:53:27 PM
If you set up multiple connections within the data source, Cognos will have them choose which one. You should be able to preset the username/password on one connection, and prompt for the other. But as far as I know it is always going to ask which connection they want to use, so it might annoy your regular, service-account-based users.

The trick is to secure each signon so that a user has permissions only to one. In this case, no prompting is done. Grant Traverse, Read and Execute privileges to the user or group you wish to use the signon, and no privileges for other users.

Cheers!

MF.
Meep!

MFGF

Quote from: MFGF on 17 Jul 2015 03:21:04 AM
The trick is to set up multiple signons within one data source connection, and secure each signon so that a user has permissions only to one. In this case, no prompting is done. Grant Traverse, Read and Execute privileges to the user or group you wish to use the signon, and no privileges for other users.

Cheers!

MF.
Meep!