Some companies
do not like to store user passwords in metadata. This is often true
when third-party databases, such as Teradata, Oracle, or DB2, are
used. For third-party databases, you might be given a credential directly
in your metadata logon object or via a group membership with a shared
credential. In either case, you will be notified that your database
credential information is missing.
When you
are denied access to view a report because of missing database credential
information, SAS Web Report Studio gives you the opportunity to enter
a valid user ID and password. When you enter your user ID and password,
they are valid for the current session only because they are stored
in memory, not in metadata.