Hi,
Is it possible to configure an FM setup to use AD as authentication rather than the default authentication used in cognos connection?
We have a gateway as well, but the gateway was configured to use the default authentication.
I'm looking as well a way to include camnamespace in the gateway uri, maybe this can be a work around.
Let me know what you think.
Quote from: sdf on 17 Aug 2018 02:14:48 PM
Hi,
Is it possible to configure an FM setup to use AD as authentication rather than the default authentication used in cognos connection?
We have a gateway as well, but the gateway was configured to use the default authentication.
I'm looking as well a way to include camnamespace in the gateway uri, maybe this can be a work around.
Let me know what you think.
Hi,
FM doesn't perform authentication per se - it uses the authentication provider or providers defined in the Cognos instance it is configured to work with. The calls to the authentication provider are handled by the Content Manager part of the processing tier. If you want to use a second authentication provider, you can configure one, but it will be available for all users of the Cognos instance, and you will also need to define security rules / capabilities for its users, as they will be a different set of users with different CAMIDs from the users in your current provider. What are you trying to achieve?
MF.
What I am trying to have is for FM to use AD authentication.
AD and another authentication provider is setup in CM. Its just that cognos connection is defaulted to use the CJAP authentication and users must not be able to login using AD.
We are limiting the use of FM for the dev only. That's why we are setting it up to default to AD instead.