Previous Page | Next Page

Administering SAS BI Web Services

Configuring SAS BI Web Services for .NET

If you are using SAS BI Web Services for .NET, then you can change the configuration settings for generated Web services by editing a web.config file. The following configuration settings can be edited manually in the web.config file:

NamespaceForGeneratedServices

specifies the namespace that a generated Web service uses.

AuthenticationType

specifies one of the following two values:

Trusted

The Web service is configured (in the SystemMetadataFile or the UserMetadataFile) with a trusted connection to the metadata server. The Web service examines the HTTP context (which means that the caller authenticates using the standard container capabilities) in order to get the current user ID, and uses that ID when connecting to the metadata server. Trusted authentication is also known as Web authentication.

Host

The middle tier authenticates against the metadata server as a non-trusted user. Host authentication is also known as SAS authentication. Using this type of authentication means:

  • If you configure the MetadataAuthenticator SecurityTokenManager (in the microsoft.web.services3 section of this configuration file), then clients might pass in credentials that get used to connect to the metadata server. This configuration is enabled by default.

  • If a client does not pass in credentials, or the MetadataAuthenticator is not configured, then a default set of credentials (which might be SSPI) needs to be set in the SystemMetadataFile or UserMetadataFile. These credentials enable callers to anonymously connect to a server (if the container is also configured to allow this connection).

  • If a Username Token is used, the user name and password are passed as plain text in the WS-Security Username Token. It is strongly recommended that you use secure HTTPs when using a plain text password.

This setting is not specific to Web services, but applies to the middle tier in general.
AcceptableSyscc

indicates which error codes do not cause a SOAP fault. After a stored process runs, the Web service checks the SYSCC macro value in SAS. If that value is not in the comma-separated list for AcceptableSyscc, then a SOAP fault is generated and the message is obtained from SYSMSG.

SystemMetadataFile

specifies the location of the system metadata file. The system metadata file contains the location (host, port, and encryption) of the metadata server, and might contain credentials.

UserMetadataFile

specifies credentials that override what is in the SystemMetadataFile setting. To force callers of the service to specify credentials on each call, you should not provide default credentials for either the SystemMetadataFile or the UserMetadataFile settings.

ClientName

is passed to the stored process at run time at the start of the _CLIENT macro.

Previous Page | Next Page | Top of Page