Online Documentation for SQL Manager for SQL server
Setting protocol options
The Protocol tab allows you to specify HTTP/TCP protocol options pertaining to the endpoint.
Specify the URL path that identifies the location of the endpoint on the host computer. This string is a logical partitioning of the URL namespace that is used by the listener to route requests appropriately.
Specify the authentication type(s) to be used to authenticate users that log on to the instance of SQL Server:
It is one of the two required authentication mechanisms in the HTTP 1.1 specification. Basic authentication is made up of an Authentication header that contains the base64-encoded user name and password separated by a colon.
It is the second authentication mechanism required by HTTP 1.1. This authentication is made up of the user name and password. This is then hashed with MD5, a one-way hashing algorithm, and sent to the server. The server has access to either the raw password, or a stored MD5 hash that was created when the password was set. The server can then compare the stored calculated value to the one provided by the client. This way, the client can prove that it knows the password without actually giving it to the server.
Endpoints configured to support integrated authentication can respond with either of the following authentication types as part of the authentication challenge: Kerberos or NTLM. Under this configuration, the server will try to authenticate the client with whichever type the client uses in requesting authentication.
It is the authentication mechanism supported by Windows 9x and Windows NT 4.0 (client and server). This authentication mechanism is a challenge-response protocol that offers stronger authentication than either basic or digest. NTLM is implemented in Windows 2000 and later versions by a Security Support Provider Interface (SSPI).
This authentication is an Internet standard authentication mechanism. Kerberos authentication is supported in Windows 2000 and later versions by an SSPI. When Kerberos authentication is used, the instance of SQL Server must associate a Service Principal Name (SPN) with the account it will be running on.
Use this group to specify the listening port type(s) to be associated with the endpoint:
Specify the hint that returns to the client, which sent the SOAP request to the endpoint, as part of HTTP authentication challenge (applied when Authentication is set to Digest).
Specify the default login domain (applied when Authentication is set to Basic).
Specify the name of the host computer, or one of the specific signs:
Implies that a listening operation applies to all possible host names for the computer that are not otherwise explicitly reserved.
+ (plus sign)
Implies that a listening operation applies to all possible host names for the computer.
If this option is selected, SQL Server will honor requests where gzip encoding is accepted, and return compressed responses. That is, if a request comes in with an HTTP header specifying GZIP as a valid "accept-encoding", the server returns the response gzip-encoded.
When TCP/IP is enabled for SQL Server, the Database Engine will listen for incoming connections on a connection point consisting of an IP address and TCP port number.
Specify the port number that will be listened to for connections by the service broker TCP/IP protocol. The default port number is 4022.
Specifies the IP address that the endpoint will listen on.