Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Security Features in Cognos.Need input

Security Features in Cognos.Need input

Security Features in Cognos.Need input

Hello Team,
We are evaluating various tools such as Microstrategy,Business objects and Cognos. I would like to know about the security features available in Cognos product. Can anybody guide me to know more about it.

RE: Security Features in Cognos.Need input

It has been awhile for me but last time I checked there were several layers of security.  Using the catalog as the repository, you can assign passwords to individual users and grant or deny access to individual tables, views, or data elements within tables.  Don't know if it is still true but Impromptu was (maybe is) known for it's flexible and powerful admin/security functionality.  One word of caution, getting very fancy with the setup of access security may result in a significant amount of maintenance later.  There is always a price to be paid, as they say.

RE: Security Features in Cognos.Need input

Powerplay: You can protect a Powerplay Model/PowerCube by password or more granularly by member class; i.e: The National Manager can see everything, the Northeast Manager can see his region and his subordinates, the NY rep can only see his territory. You can also create views of a model based on a user class.


RE: Security Features in Cognos.Need input

The overall underlying security respository is LDAP. The users and user classes are stored there and then the user classes are applied to the various products (the user classes allow more flexibility and less overhead than individual user security). As users come in and out of the various user classes you won't need to rebuild all of your objects/reports. The security can be applied as detailed as your business requires, however there are always trade-offs when you get very detailed.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close