Automatically renew trusted credential

How do I choose the value to use for the Security > Authentication > Automatically renew trusted credential setting?

Answer

For IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.
The credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration.

  • Primary namespace only (default setting): When you log on to the first namespace of your session, if you have trusted credentials for that account, the credentials are updated for the primary account only. All other credentials for other namespaces are not updated.
  • Off: Credentials are not updated in any namespace.
  • All namespaces: When you log on to the first namespace, your credentials are updated as described for "Primary namespace only". When you log on to additional namespaces, if your trusted credentials associated with the primary account contain logon information for that namespace, then those trusted credentials are updated. NOTE: Do not use the All namespaces option if users authenticate into secondary namespaces as different users.

A user's trusted credentials for a namespace will only be renewed once per day.

Comments

Post a Comment

Popular posts from this blog

How can you extract all user information from Cognos Access Manager Namespace Report Utility and create Cognos Report out of it?

The AM_NamespaceReport Utility allows you to extract the namespace to an XML file. 1. Use the AM_NamespaceReport Utility to extract all users from the namespace to an XML file. am_namespacereport -h > -p > -r > -n > -D > -w > -f all -o > e.g am_namespacereport -h cognoscamsevr -p 4004 -r o=cognos.com –n devcam -D admin -w admin -f all -o c:\temp\usrlst.xml 2. This will extract all user information to an XML file 3. Import the xml file into XLS spread sheet 4. Create ODBC connection using the ms-excel spread sheet driver 5. Create Data Source Connection and proceed creating FM Model & Publish 6. Create Report using Report Studio. 7. Save & Share the report The Access Manager Administration Guide (Appendix A) contains further information on this functionality.
Read more

RSV-VAL-0032 expression is not valid. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'.

Image
Problem: RSV-VAL-0032 The following expression is not valid: [AdjRowsReturned] = 0. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'. The variable named '[AdjRowsReturned]' is invalid Resolution: You might have used the calculated data item in the variable, which needs to be added in the page properties. - Click on the page and go to properties. Make sure you see 'page' on the top of the properties. - Click on properties icon under data section, you'll get pop up icon - Check mark the data item which is used for variable calc. You are good to go.Find the snapshot. .
Read more

BME-EX-0047 Unable to read preferences for the requested interface..

Issue When opening or creating a Framework Manager project the following error message is shown. Additionally, when attempting to create or open a report based on a package is made in Report Studio or Query Studio, the same error message is shown. Error BME-EX-0047 Unable to read preferences for the requested interface. Please use another repository and/or ProjectAccess Interface. Resolving the problem This happens due to a corrupt bmt.ini file in <Install Location>/c8/configuration directory. This issue can be resolved by extracting bmt.ini from last known good backup or even from installation files.
Read more