Cognos Framework Manager and Data Security on a Query Subject

[gosoccer]

Hi, :D

We have established a Data Security on a Subject Query by establishing the Group and Filter as a part of
Framework Manager's Data Security option.

In our development environment, this Data Security (established in Framework Model (FM) works just fine and only certain elements are showing in the Reports based on the Group and the Filtration.

When we move our Reports to the Production environment, the Security is not working for the selected Users who have been
assigned the selected Roles.

Is there any specific process we can go through that would tell us what's not working. OR even if there is a code we can put
in our REPORT that shows the discrepancies between what the Report Filter is looking for (Based on the FM MOdel Package deployed) and
the Production LDAP environment.

Obviously the Grouping/Filtration is not matching to what the PRODUCTION LDAP is presenting to the Reports.

Thank you in advance for your time. :) :)

[stan.parker]

The CAM ID will be different between your DEV LDAP and PRODUCTION LDAP. Create a group under the Cognos namespace in DEV and then export and import the same group into PRODUCTION.

[gosoccer]

Thank you Stan. Unfortunately, I don't have access to this environment to import. I take it the Admin can do a comparison between
the CAM IDs from the two environments? There is no way to add a code to the TEST Report to return with PROD CAM ID?

[stan.parker]

Can you ask the admin to add the PROD LDAP as security source in your DEV environment? If the PROD LDAP is available in your DEV environment you can add your data filters for both DEV and PROD at the same time.

[gosoccer]

Ok, sounds like a good plan Stan. I'll talk to him and see what comes out of it. Thanks again

[stan.parker]

Did it work?


Sent from my iPhone using Tapatalk

[gosoccer]

Thank you for asking.

Since we don't have any access to the Prod Region, the System Admin took a copy of our Framework Model and reviewing to see what could be the problem. The Namespace/Ream are the same between the two environment as we checked so it may gets even deeper.