Adding a WSDL or SOAP Data Source

URL to the WSDL or SOAP data source. WSDLs can be available by URL over any accessible network. A locally mapped WSDL can be introspected using a URL format like the following:

file:///Z:/test.wsdl 

Optionally, provide a valid username to the data source.

Optionally, provide a password to the data source.

This check box is enabled only if Pass-through Login is enabled. Refer the User Guide, Section About Pass-Through Login for more information.

Disabled—The default setting. This allows automated provisioning of a connection pool. If Pass-through Login is disabled, the Save Password check box is not available.

Enabled—A new connection to the data source uses the credentials supplied by the client when data is requested from that data source for the first time. If Pass-through Login is enabled, the Save Password check box becomes available.

Refer the User Guide, Chapter About Pass-Through Login for more information.

Choose the method of authentication for this data source: BASIC, NTLM, or NEGOTIATE, OAuth, Digest.

When selecting OAuth as the authentication mode, another tab will display. Authentication for the data source must be designated as OAuth 2.0 when the physical data source was first added.

For NTLM authentication only, enter the domain.

See “Configuring NTLM Authentication” in the TDV Administration Guide for more information.

For NEGOTIATE authentication with Kerberos only, enter the service principal name.

See “Configuring Kerberos Single Sign-On” in the TDV Administration Guide for more information.

These OAuth flows:

Used in the request-body of token requests. A unique string representing the identifier issued to the client during registration. It is exposed to the resource owner. Format: string of printable characters.

Used in the request-body of token requests. Enabled only for AUTHORIZATION_CODE, and OAuth flow. Format: string of printable characters.

URI to use for establishing trust and obtaining the required client properties.

URI to use for communicating access and refresh tokens to the client or resource server. Disabled only for IMPLICIT OAuth flow.

Client’s redirection end point, established during client registration or when making an authorization request. Must be an absolute URI, and must not contain a fragment component. The authorization server redirects the resource owner to this end point.

Authorization scope, which is typically limited to the protected resources under the control of the client or as arranged with the authorization server. Limited scope is necessary for an authorization grant made using client credentials or other forms of client authentication. Format: one or more strings, separated by spaces.

A request parameter used in lieu of a complete redirection URI (if that is not available), or to achieve per-request customization

The lifetime of the access token.

Checking this box enables the use of refresh tokens to obtain access tokens, rather than obtaining them manually.

User credentials with which the client or resource owner registers with the authentication server before initiating the OAuth protocol.

Enabled or Disabled

BASIC, DIGEST, NTLM, or NEGOTIATE—The usual collection of authentication methods, used for registration with the authentication server.

Domain to which the client or resource owner belongs; for example, composite.

SPN of the client or resource owner.

Bearer—User of a bearer token does not need to prove possession of cryptographic key material. Simple inclusion of the access token in the request is sufficient.

Query—The query string “?access_token=<token>” is appended to the URL. Not available for SOAP data sources.

Credentials used to access protected resources, with a specific scope and duration. Usually opaque to the client.

Initiates acquisition of an access token. Proper information must be configured for this request to succeed.

Credentials used to obtain access tokens when they become invalid or have expired. Intended for use with authorization servers, not resource servers.

The name of the custom flow for a data source with an OAuth flow of CUSTOMIZED.

Check this box to use processors. The editable text field allows you to enter JavaScript and XML. You can use this field to add JavaScripts that log in automatically or use XML to customize any part of the authorization or access token that does not conform to specifications.

Editable text field

The editable text field underneath the Using Processors check box can be used to type the XML elements necessary to establish authorization and access tokens. For example:

<Authorization>  <AuthorizationProcessors>  

<AuthorizationProcessor>    document.getElementById('email').value='queenbeeza@gmail.com'; document.getElementById('pass').value='jellypassword'; document.getElementById('loginbutton').click();  </AuthorizationProcessor>  </AuthorizationProcessors>  </Authorization> 

<AccessToken> <RequestMsgStyle>QUERY</RequestMsgStyle> <ResponseMsgStyle>FORM</ResponseMsgStyle> 

<ExpireTime>1000</ExpireTime> </AccessToken>