Share via

DataSourceDefinition.CredentialRetrieval Property

  • Reference

Definition

Namespace:
ReportService2005
Assembly:
ReportService2005.dll

Indicates the way in which the Report Server retrieves data source credentials.

public:
 property ReportService2005::CredentialRetrievalEnum CredentialRetrieval { ReportService2005::CredentialRetrievalEnum get(); void set(ReportService2005::CredentialRetrievalEnum value); };
public ReportService2005.CredentialRetrievalEnum CredentialRetrieval { get; set; }
member this.CredentialRetrieval : ReportService2005.CredentialRetrievalEnum with get, set
Public Property CredentialRetrieval As CredentialRetrievalEnum

Property Value

CredentialRetrievalEnum

A CredentialRetrievalEnum value which indicates the way in which the report server retrieves data source credentials.

Remarks

You can use the CredentialRetrieval property to specify where to retrieve the credentials that are to be used by the Report Server when connecting to an external data source.

There are four possible settings for this property:

  • None – The connection to the data source does not require connections. This is the least secure method of connecting to an external data source and is not recommended. Note The UnattendedExecutionAccount must be specified in the RSReportServer Configuration File file.

  • Prompt - The report server requires credentials. If credentials are not supplied, the report is not generated and an exception is raised.

  • Integrated- The report server utilizes the credentials of the user authenticated to the report server. Any other data source credentials supplied are ignored.

    Note

    If the EnableIntegratedSecurity system property is set to false, setting CredentialRetrieval property to Integrated will cause an exception to be thrown when the server attempts to retrieve data source credentials.

  • Store – The credentials are stored securely in the Report Server database.

There are a number of features of the Report Server that require the credential retrieval option to be either Store or None in order to successfully execute. These include schedule based features such Report Execution Snapshot generation, Report History generation, and subscriptions.

When credentials and the connection string are stored in the Report Server database, they are encrypted.

Applies to