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

Object Security in Framework Manager 8.4

Started by ernx, 19 Oct 2010 11:33:12 AM

Previous topic - Next topic

ernx

I have a framework model (version 8.4) with data security and object security implemented in many itens based in Groups and Roles created with Access Manager(each User belong to some Role).

If I publish the package with your security in the server where the framework model was created and modified, the model works fine. But, if I copy the model to other server and to publish in local Cognos Connection, it not work. The objects in the package to the user logged aren't correct according to implemented security.

I tried in to do the same process in different machines and result not changed. Only work if to delete groups and roles in the framework model and to add again in the new server (the  CAMIDs of Groups and Roles are equal in both servers) . Therefore, the object security only work if I implement again the whole security structure (the framework model over 40000 itens...). The repeats problem if I build one export file of package in server where framework model has been created and deploy in the new server.

Somebody know what is happenning?

Thanks!

MFGF

Hi,

For this to work, the two servers would need to be pointing at the same security provider (ie the same Access Manager namespace in the same Directory server).

Is this the case?

Regards,

MF.
Meep!

ernx

Quote from: MFGF on 19 Oct 2010 04:12:34 PM
Hi,

For this to work, the two servers would need to be pointing at the same security provider (ie the same Access Manager namespace in the same Directory server).

Is this the case?

Regards,

MF.

Hi MF,

Thanks for your response, but this not resolved the problem. However, I discovered who the namespace id of the servers have to be equals (case sensitive differentiation) and in my situation this was not happening: the namespace id of one server had been setted as 'Default' and the other server was as 'default'. When I made this change, the security worked normally.

Thanks!