DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016

Size: px
Start display at page:

Download "DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016"

Transcription

1 DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016

2 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol 3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to biovia.support@3ds.com, or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA USA

3 Contents Chapter 1: Introduction 1 SOAP Web Services 1 Web Services Description Language (WSDL) 3 RESTful Web Services 4 Additional Information 4 Chapter 2: Web Services Integration Components 6 Choosing the Appropriate Component 6 HTTP Connector 7 To use the HTML Connector component to GET data, authenticating with Basic HTTP Authentication: 7 To use the HTML Connector component with a custom header to return JSON data: 9 To use the HTML Connector component with a custom header to return XML data: 11 To use the HTML Connector component to POST data with URL encoded parameters: 13 To use the HTML Connector component to POST data with a request body: 14 SOAP Connector 15 SOAP RPC Connector 19 SOAP RPC Connector (Queued) 20 SOAP Method 20 Chapter 3: Accessing Web Services with Security 21 Accessing Web Services with HTTP Authorization 21 Adding Username and Password to URLs 21 HTTP Transport Security Settings 22 Pass-through Authentication 22 Accessing Web Services with SOAP and WS- Security 23 SOAP Message Security Settings 23 Pass-through Authentication 24 Using WS-SecurityPolicy 25 Using the SOAP Connector 25 SAML 2.0 Sender Vouches 28 Configuring SAML support in the Admin Portal 29 Establishing Trust Relationships for SAML 30 Adding Trust Entries 31 Obtaining a protocol specific WSDL 33

4 Chapter 1: Introduction Pipeline Pilot includes many components that work with various web service technologies such as SOAP, WSDL and RESTful web services. These components help you integrate remote services into your pipelines by mapping input and output parameter to data records. SOAP Web Services Pipeline Pilot can integrate generic HTTP or SOAP calls to access services on remote machines. In simplistic terms, SOAP = HTTP + XML. SOAP uses XML to exchange messages with remote services, typically over HTTP. SOAP's use of XML allows any system on any platform to read and process the information. It is an ideal way to integrate disparate applications. SOAP itself refers to the "envelope" that surrounds the actual operation input and output messages. SOAP Connector s workflow to invoke a Calculate Statistics web service on a remote host The figure above shows the general pattern used to access SOAP-based services. A client application builds a message containing a SOAP Envelope and the XML-based request message. The client then Introduction Page 1

5 sends this to the service provider by transmitting an HTTP POST request with the full SOAP request message in the POST body. The following is an example of a SOAP request message: Example SOAP request created by the SOAP Connector component The SOAP Envelope contains at most two parts: one SOAP Header and one SOAP Body element. The SOAP body maps the request message to some operation on the service and conveys the input data to that operation. In practice, the SOAP header element is optional but frequently includes Quality of Service configuration for aspects like security or addressing. SOAP headers also keep application-specific configuration details separate from the operation input or output messages. The remote server unpacks the SOAP request message, invokes the target operation ("Compute Statistics" in this example) and gathers the results data. The remote server re-packs the operation results into a SOAP response message and returns this message in the HTTP POST response. The following is an example of a SOAP response message: Page 2 Pipeline Pilot Developer Guide

6 Example SOAP response message handled by the SOAP Connector You can use SOAP to integrate your third party and in-house applications on remote computers. To call a service published on your intranet, add a SOAP Connector to your protocol, as shown in this example. The SOAP Connector sends the necessary data to the service, collects the results, and continues processing within the protocol. The SOAP component sends the molecular structure to the server and adds the result to the current record. Pipeline Pilot's SOAP components allow you to access existing services on your network and incorporate them in your workflow. You can use them to read data into the pipeline and make calls within the protocol to send data associated with a record to external applications or calculator services. When the results of these services are returned to the protocol, they are added to the current data record. You can also include other standard filtering and property calculator components in your pipeline with SOAP components. You can make a variety of services accessible, such as property calculators (e.g., ClogP, 3D properties, ADME), scientific applications (e.g., docking, 2D/3D structure optimization), or legacy code. Web Services Description Language (WSDL) Web Services Description Language (WSDL) is an XML-based language for defining web services interfaces typically SOAP-based web services. It describes the request and response message formats used by the web service. Clients can read the WSDL to determine what operations a remote service provides. A WSDL file also embeds or references any special data types in the form of XML Schemas. The Introduction Page 3

7 client can then use SOAP to call one of the operations listed in the WSDL and then understand the response. Modern SOAP services nearly always provide a WSDL file that describes their interface requirements. Many services also embed or reference WS-Policy files. WS-Policy files describe the Quality of Service features supported and required by the service provider. Examples of Quality of Service features include security (authentication and authorization), addressing, integrity, and confidentiality. Pipeline Pilot SOAP components provide support for most WSDL files and many WS-Policy features as described below. RESTful Web Services Web services using the principles of REpresentational State Transfer (REST) offer an alternative to SOAP. With RESTful web services, the emphasis is on existing infrastructure used by browsers to access the World Wide Web URLs as locations for data and services, and the methods that make up the Hypertext Transfer Protocol (HTTP) to carry out the desired behavior. RESTful web services define multiple end-points, normally one URL for each entity that is part of the service. For example, a RESTful service that calculates the average of a set of numbers would be located at whereas the URL for another service that calculates the median would be at In another example, a data source (e.g., a list of molecules), is stored at To access a single molecule, a typical RESTful URL would be the second molecule would be located at and so on. To carry out some action on the resource specified by a RESTful URL, you would send an HTTP request to it. The request consists of one of the HTTP methods, headers, and (where necessary), the data associated with the request. For example, passing a GET request to a URL is interpreted as a request to return the data associated with the resource. To update the data associated with a URL, you would send a POST request, along with some data. There is a convention around which HTTP methods will carry out which action. For example, a PUT request is used to create a resource. To add this to your list of molecules, you would send a PUT request to along with the data you want to associate with that molecule. Subsequent GET requests to would return that data. In general, RESTful web services are much simpler to access and experiment with than SOAP-based services. Often, only a web browser is required to read a data source. Updating and creating RESTful data can be achieved using simple command-line tools and browser add-ons. However, there is no equivalent to WSDL and WS-Policy files for RESTful web services. Discovering exactly how resources are mapped to URLs and what data needs to be passed with each HTTP method requires finding and researching available API documentation. Pipeline Pilot provides the HTTP Connector component for accessing web services from within a protocol. It is also possible to expose protocols as RESTful web services. For further details, see the RESTful Web Services Guide in the Pipeline Pilot Help Center (Developers tab). Additional Information For more information about the Integration collection for Pipeline Pilot and other BIOVIA software products, visit For more information on SOAP 1.2, visit For more information on WSDL 1.1, visit Page 4 Pipeline Pilot Developer Guide

8 For more information on OASIS' WS-Security specification, visit For more information on WS-Policy 1.2, visit Introduction Page 5

9 Chapter 2: Web Services Integration Components Several SOAP components are available for sending the necessary data to the SOAP server, collecting the results, and adding the data to the current record in a protocol. These components are available with and without WSDL support, including the following: HTTP Connector: Generic HTTP client component that can connect to HTTP-based services, such as RESTful web services, using most HTTP calling conventions. SOAP Connector: Parses WSDL 1.0 or 1.1 files and generates new components for each operation in the WSDL file. This component simplifies integration with modern Document-literal and RPC-literal style SOAP services. SOAP RPC Connector: Similar to the SOAP Connector, but best suited to legacy RPC-encoded SOAP methods or Document-Literal styles SOAP services with simple XML messages. SOAP RPC Connector (Queued): Variation that adds support for queued processing to help increase pipeline throughput. Several concurrent calls to the SOAP server SOAP Method: Enables you to make a SOAP call to legacy RPC-encoded services. This component provides no support for WSDL interpretation. Note: From the Components tab, all SOAP components are located in Database and Application Integration\Application Integration\Web Service Integration. Choosing the Appropriate Component There are several ways to integrate HTTP and SOAP-based service calls in Pipeline Pilot. The following matrix suggests the appropriate component to choose, based on different use cases. If one of the standard SOAP Method or the SOAP Connector components cannot integrate a service, the HTTP Connector or server-side scripting components provide a useful alternative. To integrate a service: Document-literal or RPCliteral style SOAP services with WSDL files RPC-encoded and simple Document-literal SOAP services with WSDL files RPC-encoded SOAP services with no WSDL file SOAP-based services not supported by the components above Use this component: SOAP Connector SOAP RPC Connector SOAP RPC Connector (Queued) SOAP Method HTTP Connector Java (on Server).NET (on Server) Web Services Integration Components Page 6

10 To integrate a service: HTTP-based calls and RESTful web services Use this component: To GET data, use any Reader component and set the Source parameter to an HTTP URL. Reader components are optimized to efficiently stream data from HTTP sources. To DELETE, GET, POST, or PUT data, use the HTTP Connector. This component provides more control over the HTTP communication. HTTP Connector The HTTP Connector is a generic HTTP client component. Use this component to make remote HTTP calls to a resource or service (e.g., RESTful web services). The Source parameter specifies the URL location of the service or resource. Set the HTTP Method parameter to any valid HTTP verb (e.g. GET, POST, PUT, DELETE, HEAD, etc.) to perform that command. Some commands, like POST, require body parameters. Provide individually named parameters under the Parameters group or provide the entire body content using the Request Body parameter. Parameters are name-value pairs. The Value parameters are ExpressionType by default. Specify the name of a data property or a literal value for each. HTTP Connector writes response data to an output data property by the Put Response in Property parameter. The component can also write response headers to the output data record according to the Include Response Headers parameter. Use a converter component such as XML to Data to transform the output content to a usable set of properties or nodes. The simplest use of a RESTful web service is to GET existing data represented by a URL. The example below uses the REST API offered by Clever, a data platform for student information services. Both the structure of its API and the documentation are excellent examples to follow when creating your own API. As well as seeing how to use GET to fetch existing data from an account, the example also accesses the data using Basic HTTP Authentication, a common form of authentication for simple RESTful web services. The data returned from the web service is in JSON format, which is used more frequently in RESTful web services than the more verbose XML. A Data from XML component is available if the web service returns the response in XML format instead. To use the HTML Connector component to GET data, authenticating with Basic HTTP Authentication: 1. In Pipeline Pilot Client, add an HTML Connector component to a new protocol. 2. Add a Data from JSON component and connect it to the Pass port on the HTML Connector component. 3. Add a Data Record Tree Viewer component and connect it to the Pass port on HTML Connector component. Your protocol should look like this: Page 7 Pipeline Pilot Developer Guide

11 4. Configure the HTTP Connector component as follows: Parameter Source HTTP Authentication Options - Username HTTP Authentication Options - Password HTTP Method Setting DEMO_KEY Leave blank GET The filled-out parameters for the HTTP Connector are shown below: By default, the HTTP Connector takes the response from the web service and puts it as a string into a property called "Response". To do useful work with the response, you could parse the text into a data record that is almost certainly tree-like and hierarchical. 5. In the Data from JSON protocol, enter the JSON Property as "response", and set the Join Behavior to "Replace" (this removes any properties that were present on the data record, leaving only the parsed response). This saves you from having to manually remove the original response string, now that it s parsed and has no further use for the raw output. 6. Run the protocol. The results are displayed in the Data Record Tree View. When fully expanded, it should look like this: Web Services Integration Components Page 8

12 If you do not see all the data (e.g., the "location" and "principal" data are unexpanded), click on the data to expand it. The web service returned hierarchical data in JSON format, and the Data from JSON component converted it into a series of hierarchical data records (shown as the green circles), with properties indicated by the purple diamonds under each node. This is a very typical data structure expected from a web service. As noted above, the most common formats that RESTful web services return are XML and JSON. Some services only provide one format, and others will let you choose formats. If you prefer a particular form of output, you can provide this information as a header in the HTTP request. To use the HTML Connector component with a custom header to return JSON data: 1. In Pipeline Pilot Client, add an HTML Connector component to a new protocol. 2. Add a Data from JSON component and connect it to the Pass port on the HTML Connector component. 3. Add a Data Record Tree Viewer component and connect it to the Pass port on HTML Connector component. Your protocol should look like this: Page 9 Pipeline Pilot Developer Guide

13 4. Configure the HTTP Connector component as follows: Parameter Source Additional Request Headers Header 1 - Name Additional Request Headers Header 1 - Value Setting Accept application/json The filled-out parameters for the HTTP Connector are shown below: 5. In the Data from JSON protocol, enter the JSON Property as "response", and set the Join Behavior to "Replace". 6. Run the protocol. The results will be displayed in the Data Record Tree View and should look like this: Web Services Integration Components Page 10

14 To use the HTML Connector component with a custom header to return XML data: 1. In Pipeline Pilot Client, add an HTML Connector component to a new protocol. 2. Add a Data from JSON component and connect it to the Pass port on the HTML Connector component. 3. Add a Data Record Tree Viewer component and connect it to the Pass port on HTML Connector component. Your protocol should look like this: 4. Configure the HTTP Connector component as follows: Parameter Source Additional Request Headers: Header 1 - Name Additional Request Headers:- Header 1 - Value Setting Accept application/xml The filled-out parameters for the HTTP Connector are shown below: Page 11 Pipeline Pilot Developer Guide

15 5. Configure the Data from XML component as follows: Parameter Setting Property Name Response Leaf Elements Are Properties Join Behavior Replace The filled-out parameters for Data from XML are shown below: 6. Run the protocol. The results will be displayed in the Data Record Tree View and will look like this: Web Services Integration Components Page 12

16 The parsed data structure is effectively identical to what we got when we asked for JSON. In this way, you can be agnostic about whether a web service is returning XML or JSON into your protocol. The next example is intended to pass data to the PubChem REST-like Power User Gateway to find the PubChem identifier from an InChI string. Instead of the GET method we've been using up until now, this next example uses a POST. In this way, we can specify parameters to pass to a resource as separate values, which can be convenient when there are multiple parameters to organize and pass through to the service. To use the HTML Connector component to POST data with URL encoded parameters: 1. In Pipeline Pilot Client, add an HTML Connector component to a new protocol. 2. Add a Data from JSON component and connect it to the Pass port on the HTML Connector component. 3. Add a Data Record Tree Viewer component and connect it to the Pass port on HTML Connector component. Your protocol should look like this: 4. Configure the HTTP Connector component as follows: Parameter Source HTTP Method HTTP Method: HTTP Body Content Parameters: Parameter 1 - Name Parameters: Parameter 1 - Value Setting POST FormURLEncoded inchi inchi=1s/c3h8/c1-3-2/h3h2,1-2h3 The filled-out parameters for the HTTP Connector are shown below: Page 13 Pipeline Pilot Developer Guide

17 5. In the Data from JSON protocol, enter the JSON Property as "response", and set the Join Behavior to "Replace". 6. Run the protocol. The results will be displayed in the Data Record Tree View and look like this: Using POST with parameters is convenient if you have many, short parameters to provide to a service. If you are looking to provide a small amount of larger data (e.g., uploading a molecule in SD format to a service), it's more convenient to provide the body of the request manually. The next example is to the same URL with the same data as we just carried out. But this time, we're going to use the request body rather than separate parameters. However, we should still get the same result. To use the HTML Connector component to POST data with a request body: 1. In Pipeline Pilot Client, add an HTML Connector component to a new protocol. 2. Add a Data from JSON component and connect it to the Pass port on the HTML Connector component. 3. Add a Data Record Tree Viewer component and connect it to the Pass port on HTML Connector component. Your protocol should look like this: 4. Configure the HTTP Connector component as follows: Parameter Source HTTP Method HTTP Method: HTTP Body Content Request Body Request Body: Content-Type Setting POST Send Request Body inchi=inchi=1s/c3h8/c1-3-2/h3h2,1-2h3 application/x-www-form-urlencoded The filled-out parameters for the HTTP Connector are shown below: Web Services Integration Components Page 14

18 5. In the Data from JSON protocol, enter the JSON Property as "response", and set the Join Behavior to "Replace". 6. Run the protocol. The results will be displayed in the Data Record Tree View and should look like this: SOAP Connector The SOAP Connector components provides robust access to modern Document-Literal and RPC-Literal style SOAP services. SOAP Connector works like other WSDL-supported components. It parses a WSDL file and parameterizes a new instance of the component for each SOAP operation. However, the SOAP Connector simplifies the process of mapping data record properties to complex SOAP request messages by providing a set of Expression Type parameters. Each parameter corresponds to an XML attribute or elements in the SOAP request message. The SOAP Connector supports SOAP header and body parameter mapping. The SOAP Request parameter group (shown below) contains Header and Body parameter groups. These parameters map one-to-one with elements written to the SOAP request envelope. If the specified WSDL file defines any SOAP headers, the corresponding parameters will be children of the Header parameter group. The same is true with the Body parameters. Many WSDL files do not define headers and the Header group may contains no children. Notes: The SOAP Connector component does not yet support the following features: RPC-encoded web services XML request messages with list or union type elements MTOM and SOAP Attachments WS-Addressing WS-Security SAML 2.0 Holder of Key pattern and WS-Security Kerberos Token Profile WS-Trust To use the SOAP Connector component: Page 15 Pipeline Pilot Developer Guide

19 1. In Pipeline Pilot Client, add a Generate Empty Data component to a new protocol. 2. Add a SOAP Connector component and connect it to the Pass port on Generate Empty Data. 3. Add an HTML Table Viewer component and connect it to the Pass port on SOAP Connector component. Your protocol should look like this: 4. Select the SOAP Connector component's WSDL parameter and click. The WSDL parameterization dialog opens. WSDL dialog before parameters are set Web Services Integration Components Page 16

20 5. In the text box, enter a valid WSDL URL. This example uses services provided by the United States Center for Operational Oceanographic Products and Services to retrieve meteorological data for Hilo Bay, HI. Their air temperature service WSDL is located here: Note: The SOAP Connector component parses WSDL files on the Pipeline Pilot server. Therefore, the WSDL URL or file references must be accessible by the Pipeline Pilot server. This is different from other SOAP method components that parse WSDL files on the Pipeline Pilot Client. 6. Click Load WSDL. The dialog displays a series of progress messages while it parses the WSDL file and then provides a new set of parameters: WSDL dialog 7. Change the port or method name list boxes to see all the provided service operations. In this example, we used the "getairtemperature" operation. Page 17 Pipeline Pilot Developer Guide

21 8. Enter parameter values for all required parameters. Parameters are expression type. In the typical case, parameter values are data record properties names, but literal expression values work just as well. This example uses literal values as follows: SOAP Request parameter values Tips: You can find information on valid parameter values and stations here: Parameter values: Station identifiers: 9. Click OK and run the protocol. The results should look something like this: Protocol results for SOAP Connector component Web Services Integration Components Page 18

22 IMPORTANT! The SOAP Action parameter normally contains information provided in SOAP 1.1 and some SOAP 1.2 bindings. If you leave this parameter blank, the SOAP Connector will not send a value for the SOAPAction HTTP header. Some services may return an error if there is no SOAPAction header. If you receive a SOAP Fault such as "faultstring: no SOAPAction header", you can send a blank value by entering a blank space in the SOAP Action parameter. SOAP RPC Connector The SOAP RPC Connector allows you to make a SOAP call to third-party services. This component uses a WSDL file to discover operations and their required input parameters. The component's WSDL dialog creates new parameters that help you map data record properties to an operations SOAP request message and then map the operations results onto new data record properties. The following is an example of the WSDL dialog used for the protocol Get Stock Quote using SOAP: WSDL dialog To configure the SOAP RPC Connector component to use a web service: 1. Select the SOAP RPC Connector component to expose its parameters. 2. Open the WSDL parameter dialog. 3. In Path to the WSDL file, specify the web service's location. Click Browse and navigate to the file. If the WSDL resides at a URL, enter the URL directly into the text box. 4. Click Load WSDL. Details about the web service are exposed in the dialog. Method Name lists all available web service methods (with the first method in the list selected). Related information for the first method is displayed in End Point, Namespace, and Action. 5. Select the method you want to call from the Method Name list. End Point, Namespace, and Action options are updated automatically. Page 19 Pipeline Pilot Developer Guide

23 Map Input Parameters displays the arguments required for the selected method. The names of the arguments are listed on the left. On the right side, enter values that correspond with the property names in your protocol. Map Return Parameters displays the return values available for the selected method. Check all return values that you want to use in your protocol. You can also change the name of the returned property by editing the values on the right. 6. Click OK to save the WSDL settings. SOAP RPC Connector (Queued) With this component, incoming data is queued for processing up to the specified limit. Processing can continue in other parts of the protocol while multiple simultaneous SOAP calls are made on the queued data. Number Threads specifies the number of simultaneous SOAP calls used to process queued data. By default, the component will not preserve the order of queue data. To preserve the order of the outgoing data to the corresponding order of the incoming data, set Preserve Order to True. SOAP Method This legacy component makes SOAP calls to RPC-encoded services. The figure below shows the parameters for the SOAP Method component with a simple stock quote example. This component uses the symbol property on the incoming data to assemble a SOAP call to the specified web service endpoint. The component places the information received from the call in the Result property and returns the data record through the Pass Port. Web Services Integration Components Page 20

24 Chapter 3: Accessing Web Services with Security Security policy is an integral part of most Services Oriented Architectures (SOA). Security policies come in many different flavors. Some services assume that the calling application has already authenticated the user and therefore they require no specific security features at the service level. In other cases, the service itself checks the user's identity and access level. Most modern services require some level of security applied to each call. You will likely encounter authentication and authorization issues at both the SOAP message and HTTP transport levels when you integrate with modern web services. SOA security is a complex topic. However, the HTTP Connector and SOAP Connector components provide features to help you securely connect to remote services. Accessing Web Services with HTTP Authorization Some web servers require HTTP-based authentication. If denied access to a URL with a "401 - Unauthorized" error message, the web service expects HTTP Transport-level authentication. The security information is called "transport-level" security because SOAP is the message format carried over the HTTP protocol or transport. HTTP-transport security may be required for the WSDL file itself and on the endpoint URL where the service executes. When authorization is required for the WSDL file, download the WSDL file to your local machine through a Web browser and point the SOAP RPC Connector component to that local copy. Modern browsers usually prompt you for a valid username and password to access the requested URL. The SOAP RPC Connector component provides methods for passing authentication information via the HTTP Authorization header. Configuring the SOAP RPC Connector component to transmit authentication details over HTTP headers is similar to the SOAP Message Security described above. Tip: For details on the HTTP Authorization RFC, visit the IETF web site at Adding Username and Password to URLs You can provide a username and password directly in the WSDL and SOAP Endpoint parameters by adding your information to the URL as follows: Here, the <username> and <password> must be given in plain text. The <host> and <port> parameters correspond to your web address. Most URL-type parameters support this method of passing authentication. Hard-coding your username and password into URL parameters has clear pitfalls. For example, your username and password are visible in plain text in the protocol XML. Therefore, only use this method when you have a shared read-only account or when you save the protocol to your User Name tab. You can also use the HTTP Transport Security Settings because they are more secure during transmission and when saving or publishing your protocol. Accessing Web Services with Security Page 21

25 HTTP Transport Security Settings The SOAP RPC Connector components provide a group of HTTP Transport Security parameters. Like the SOAP Message Security parameters, set the HTTP Transport Security parameter to True, and then use the Authentication Method, Username, and Password parameters as described above. Parameters for HTTP Transport Security Settings IMPORTANT! The SOAP RPC Connector, HTTP Connector, and SOAP Connector components supports BASIC, DIGEST, and NTLM encoding for the HTTP Authorization header information. For these components, Pipeline Pilot attempts to negotiate for a format. If the component cannot negotiate a supported encoding, it will attempt to guess the format by first sending BASIC encoding and then NTLM. If all else fails, the component will return a "401 Unauthorized" error message. To determine an appropriate method for setting up HTTP-based security, consult with your web server administrator. Tips: You can use SOAP Message Security and HTTP Transport Security parameters together. Each parameter group works independently. For instance, you can set up the SOAP Message Security for pass-through authentication and also hard-code a different username and password for the HTTP Transport Security settings. The HTTP Transport Security option is disabled by default and the SOAP Method components work the same as in previous releases. Requirements for HTTP transport security are not visible in a WSDL file because the file simply defines the format and policy of the SOAP messages. You can find HTTP transport security requirements through documentation of the remote SOAP service or by trial and error. If you receive the "401 - Unauthorized" error message when accessing a WSDL file or service endpoint, configure the HTTP Transport Security parameters. Pass-through Authentication Like the SOAP Message Security settings, you can also enable pass-through authentication at the HTTP Transport level. Page 22 Pipeline Pilot Developer Guide

26 Parameters to enable pass-through authentication over HTTP Authorization header SOAP is a method for accessing web services. HTTP (Hypertext Transfer Protocol) is a standard mode of communication over the Internet and all web servers recognize and respond to HTTP requests. XML (Extensible Markup Language) is a standard method for exchanging information across systems. Accessing Web Services with SOAP and WS-Security The SOAP RPC Connector component supports the OASIS WS-Security 1.0 specification. For details about web service specifications, see the OASIS website: SOAP Message Security Settings The SOAP RPC Connector components have a SOAP Message Security parameter group, which you can set to True to include WS-Security SOAP headers in each SOAP request. The security headers conform to OASIS' Username Token Profile 1.0 specification. Use the Token Type parameter to specify the password encoding style. Parameters for SOAP Method Security Settings Accessing Web Services with Security Page 23

27 IMPORTANT! Only plain text encoding is currently supported. Use SSL to protect your username and password credentials on the network. Ensure that your service endpoint starts with "https", and that the port corresponds to the SSL port on your web server. If your web service requires SOAP Message Security and you do not know the SSL configuration, consult your web service administrator for details on how to secure your password. Tips: The SOAP Message Security option is disabled by default. The WSDL dialog currently does not support WSDL documents with imported schema types. The workaround is to manually insert the imported schema into a copy of the WSDL document, making it possible for the WSDL dialog to properly digest the file. Web services that require WS-Security frequently use the WS-Policy specification to transmit policy information in their WSDL documents. However, the WSDL dialog does not currently support this mechanism. The workaround is to manually configure the SOAP Message Security options. If your WSDL document contains WS-Policy information and the WSDL Dialog cannot parse it, manually save the WSDL document and remove the policy details. The WSDL dialog should be able to accept the pared-down version of the WSDL document. Pass-through Authentication The SOAP RPC Connector components support pass-through authentication. To enable this feature, set the Authentication Method parameter to Use Pipeline Pilot Credentials. The Username and Password parameters are disabled when pass-through authentication is enabled. When the using the Use Pipeline Pilot Credentials option, the server automatically encodes the username and password for the current protocol user into each SOAP packet. Use this feature to pass identity and credential information to web services that support the WS-Security 1.0 specification. Parameters to enable pass-through authentication Page 24 Pipeline Pilot Developer Guide

28 Tips: For pass-through authentication to work, the Pipeline Pilot authentication method and the receiving web service must share the same domain authentication scheme. This works well when both the server and your web services provider use LDAP or Activity Directory for authentication. If the authentication method is not identical, pass-through authentication can still work, but only in cases where the username and password match the credentials used for server access. To override the Pipeline Pilot Client credentials, specify a specific username and password as separate parameters. The server encrypts any saved passwords saved in the protocol database for your protection. However, do not share your component or protocols with other users. Using WS-SecurityPolicy WS-SecurityPolicy is a standard by which web services can communicate security requirements to applications that interact with it. Among other things, a service publishing a security policy can dictate how to authenticate requests or protect responses. A policy may apply to the entire service, certain operations, or even individual messages. The security policy applies to the application layer and may supplement or replace socket level security. The specification provides a rich language for specifying security requirements to external parties. Security policies may contain one or more alternatives, which typically allow use of different types of credentials when accessing the service. For example, each alternative can conform to one of several standardized security profiles that make use of Kerberos tickets, X509 certificates, username/password pairs, or SAML assertions. Additionally, the policy may dictate encryption or signing requirements on the header or body. Using the SOAP Connector You will need to use the SOAP connector to invoke a web service that accepts WS-Security headers. Currently, the SOAP connector supports policies conforming to the UsernameToken profiles with plain text, digested, or no password. SAML 2.0 Sender-Vouches is also supported, but requires additional configuration in the Administration Portal. On the Parameters tab for the SOAP Connector, click on the WSDL parameter to display the WSDL dialog. In the dialog, load the WSDL, and select the desired port and method. You will need to use a WSDL for the service that contains a security policy. Accessing Web Services with Security Page 25

29 Note: If the WSDL does not contain an appropriate security policy, you may need to save the WSDL to your local disk and add the policy manually. After dismissing the WSDL dialog, you can select a policy alternative from the WS-Security parameter. If the alternative accepts arbitrary username/password combinations you may opt to use the "Use Username and Password Parameters" authentication method. Otherwise, select "Use Pipeline Pilot Credentials". Page 26 Pipeline Pilot Developer Guide

30 Many security policies restrict you to use the credentials that were used to authenticate the current Pipeline Pilot session. Other policies allow you to specify an arbitrary username and password, which you can do by setting the Authentication Method to "Use Username and Password Parameters". If the service accepts a UsernameToken with a plain text, or digested password but the WSDL does not contain a policy, Pipeline Pilot can insert a generic Username Token or Username Digest security header. Accessing Web Services with Security Page 27

31 SAML 2.0 Sender Vouches The Web Services Security SAML Token Profile is a standard that addresses the single sign-on problem for web services. It specifies several schemes using Security Assertion Markup Language (SAML) tokens to simplify interoperability between web services. If you wanted to invoke a service (Alice) which in turn needs to invoke a second service (Bob), without single sign on, you would have to authenticate with both services and provide some token to Alice for it to pass to Bob for authentication. However, if there is some prior trust relationship between Alice and Bob, you may invoke Bob without authenticating a second time if you are already authenticated with Alice. Your identity can be passed from Alice to Bob using one of several schemes called confirmation methods. These confirmation methods include the "Sender Vouches" method in which the sender acts on behalf of and vouches for you. Bob will process the request because Alice insists that you are the originator of the request. Bob determines the validity of the request based on whether or not it was digitally signed by Alice. Page 28 Pipeline Pilot Developer Guide

32 A single sign on setup provides greater benefit when there are many backend services. Pipeline Pilot can act as either the sender or recipient in a SAML Sender Vouches scenario. Configuring SAML support in the Admin Portal Before Pipeline Pilot can send or receive SOAP messages containing SAML assertions, you must configure SAML settings and trust relationships. You will need to generate or obtain and import an X.509 certificate and key pair. For more information, refer to Admin > Security > Certificates > Managing SSL Certificates in the Administrators tab of the Help Center. Note: Many third party application stacks require that the server name (CN) of the certificate must match the hostname of the compute on which Pipeline Pilot is running. You cannot use the generic certificate provided by default after installation. After an SSL Certificate is installed, you need to import it into the SAML Certificate page in the Pipeline Pilot Administration Portal. 1. Go to Security > SAML Certificate. 2. Click Import SSL Key Pair. 3. Set the Issuer URL to an arbitrary string. It does not need to be tied to the certificate's subject or issuer, however, it should uniquely identify the particular instance of Pipeline Pilot running on the host machine. Some combination of hostname and port number is recommended. Accessing Web Services with Security Page 29

33 4. The Time to Live and Time to Live Offset fields provide a mechanism to deal with network and processing latency as well as clock skew between the relevant services. You will need to adjust these values according to circumstances. If SAML assertions expire before they reach the remote service, increase the value for Time to Live. If assertions arrive at remote service before they are valid, according to clock of the host machine, increase the offset. Generally, the offset should be a fraction of the time to live. 5. Click Save Parameters. Establishing Trust Relationships for SAML After saving your SAML Issuer Token Parameters, you need to export certificate from Pipeline Pilot and import it into the trust store of the remote service. Click View / Export SAML Metadata to display the certificate. Page 30 Pipeline Pilot Developer Guide

34 Note: If the remote service is hosted on a different application server stack, consult its documentation regarding trust management. Generally, this involves adding the Pipeline Pilot server's SAML certificate into a trust store and mapping the Pipeline Pilot server's issuer URL to applications on the target server. Adding Trust Entries If the remote service is another Pipeline Pilot server, navigate to the Trusted Certificate tab on the remote server and paste the certificate contents into the import dialog. You may optionally specify the issuer. Accessing Web Services with Security Page 31

35 Notes: After a trust relationship is established, protocols can use the SOAP Connector to invoke web services that accept SAML assertions. To allow third-party application servers to launch protocols using SAML, create a trust entry for the remote service in this same manner. Refer to application server's documentation for instructions on configuring and exporting signing keys for SAML. Page 32 Pipeline Pilot Developer Guide

36 Obtaining a protocol specific WSDL 1. in Pipeline Pilot Client, right-click the protocol name and choose Inspect Web Service: 2. This opens a page in your web browser. Choose Blocking with WS-Security: The WSDL URL provides the location of the WSDL that an external service can use to launch the protocol: The WSDL's policy provides three alternatives when loaded into a SOAP Connector. Accessing Web Services with Security Page 33

37 3. To launch the protocol, invoke the Execute method. The Login method allows you to authenticate via WS-Security to obtain a session key. With the key returned from the Login method, invoke operations in the Polling WSDL. 4. Additionally, right-click a folder and choose Inspect Web Service to open a folder based WSDL. Note that each protocol in the folder maps to a SOAP operation. Page 34 Pipeline Pilot Developer Guide

DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016

DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA,

More information

INSTALL GUIDE BIOVIA INSIGHT 2016

INSTALL GUIDE BIOVIA INSIGHT 2016 INSTALL GUIDE BIOVIA INSIGHT 2016 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD,

More information

INSTALL GUIDE BIOVIA INSIGHT 2.6

INSTALL GUIDE BIOVIA INSIGHT 2.6 INSTALL GUIDE BIOVIA INSIGHT 2.6 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD,

More information

CLIENT SYSTEM REQUIREMENTS NOTEBOOK 2018

CLIENT SYSTEM REQUIREMENTS NOTEBOOK 2018 CLIENT SYSTEM REQUIREMENTS NOTEBOOK 2018 Copyright Notice 2017 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA,

More information

Enterprise SOA Experience Workshop. Module 8: Operating an enterprise SOA Landscape

Enterprise SOA Experience Workshop. Module 8: Operating an enterprise SOA Landscape Enterprise SOA Experience Workshop Module 8: Operating an enterprise SOA Landscape Agenda 1. Authentication and Authorization 2. Web Services and Security 3. Web Services and Change Management 4. Summary

More information

QUICK START GUIDE PROTOCOL DEVELOPMENT INTEGRATION COLLECTION 2016

QUICK START GUIDE PROTOCOL DEVELOPMENT INTEGRATION COLLECTION 2016 QUICK START GUIDE PROTOCOL DEVELOPMENT INTEGRATION COLLECTION 2016 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA,

More information

ADMINISTRATION GUIDE BIOVIA QUERY SERVICE 2018

ADMINISTRATION GUIDE BIOVIA QUERY SERVICE 2018 ADMINISTRATION GUIDE BIOVIA QUERY SERVICE 2018 Copyright Notice 2017 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA,

More information

Webthority can provide single sign-on to web applications using one of the following authentication methods:

Webthority can provide single sign-on to web applications using one of the following authentication methods: Webthority HOW TO Configure Web Single Sign-On Webthority can provide single sign-on to web applications using one of the following authentication methods: HTTP authentication (for example Kerberos, NTLM,

More information

Composer Help. Web Request Common Block

Composer Help. Web Request Common Block Composer Help Web Request Common Block 7/4/2018 Web Request Common Block Contents 1 Web Request Common Block 1.1 Name Property 1.2 Block Notes Property 1.3 Exceptions Property 1.4 Request Method Property

More information

DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016

DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA,

More information

Network Security Essentials

Network Security Essentials Network Security Essentials Fifth Edition by William Stallings Chapter 4 Key Distribution and User Authentication No Singhalese, whether man or woman, would venture out of the house without a bunch of

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Administering Web Services 12c (12.1.2) E28131-01 June 2013 Documentation for developers and administrators that describes how to administer Web services. Oracle Fusion Middleware

More information

Lesson 13 Securing Web Services (WS-Security, SAML)

Lesson 13 Securing Web Services (WS-Security, SAML) Lesson 13 Securing Web Services (WS-Security, SAML) Service Oriented Architectures Module 2 - WS Security Unit 1 Auxiliary Protocols Ernesto Damiani Università di Milano element This element

More information

SAML-Based SSO Configuration

SAML-Based SSO Configuration Prerequisites, page 1 SAML SSO Configuration Task Flow, page 5 Reconfigure OpenAM SSO to SAML SSO Following an Upgrade, page 9 SAML SSO Deployment Interactions and Restrictions, page 9 Prerequisites NTP

More information

Introduction to application management

Introduction to application management Introduction to application management To deploy web and mobile applications, add the application from the Centrify App Catalog, modify the application settings, and assign roles to the application to

More information

GETTING STARTED WITH INSIGHT PLUGINS GUIDE BIOVIA INSIGHT 2018

GETTING STARTED WITH INSIGHT PLUGINS GUIDE BIOVIA INSIGHT 2018 GETTING STARTED WITH INSIGHT PLUGINS GUIDE BIOVIA INSIGHT 2018 Copyright Notice 2017 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA,

More information

FlexParts DELMIA Apriso 2018 Implementation Guide

FlexParts DELMIA Apriso 2018 Implementation Guide FlexParts DELMIA Apriso 2018 Implementation Guide 2017 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA,

More information

Setting Up Resources in VMware Identity Manager (On Premises) Modified on 30 AUG 2017 VMware AirWatch 9.1.1

Setting Up Resources in VMware Identity Manager (On Premises) Modified on 30 AUG 2017 VMware AirWatch 9.1.1 Setting Up Resources in VMware Identity Manager (On Premises) Modified on 30 AUG 2017 VMware AirWatch 9.1.1 Setting Up Resources in VMware Identity Manager (On Premises) You can find the most up-to-date

More information

Integrating VMware Horizon Workspace and VMware Horizon View TECHNICAL WHITE PAPER

Integrating VMware Horizon Workspace and VMware Horizon View TECHNICAL WHITE PAPER Integrating VMware Horizon Workspace and VMware Horizon View TECHNICAL WHITE PAPER Table of Contents Introduction.... 3 Requirements.... 3 Horizon Workspace Components.... 3 SAML 2.0 Standard.... 3 Authentication

More information

SOA Software Policy Manager Agent v6.1 for WebSphere Application Server Installation Guide

SOA Software Policy Manager Agent v6.1 for WebSphere Application Server Installation Guide SOA Software Policy Manager Agent v6.1 for WebSphere Application Server Installation Guide Trademarks SOA Software and the SOA Software logo are either trademarks or registered trademarks of SOA Software,

More information

Nimsoft Service Desk. Single Sign-On Configuration Guide. [assign the version number for your book]

Nimsoft Service Desk. Single Sign-On Configuration Guide. [assign the version number for your book] Nimsoft Service Desk Single Sign-On Configuration Guide [assign the version number for your book] Legal Notices Copyright 2012, CA. All rights reserved. Warranty The material contained in this document

More information

C exam. IBM C IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile. Version: 1.

C exam.   IBM C IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile. Version: 1. C9510-319.exam Number: C9510-319 Passing Score: 800 Time Limit: 120 min File Version: 1.0 IBM C9510-319 IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile Version: 1.0 Exam A QUESTION

More information

esignlive SAML Administrator's Guide Product Release: 6.5 Date: July 05, 2018 esignlive 8200 Decarie Blvd, Suite 300 Montreal, Quebec H4P 2P5

esignlive SAML Administrator's Guide Product Release: 6.5 Date: July 05, 2018 esignlive 8200 Decarie Blvd, Suite 300 Montreal, Quebec H4P 2P5 esignlive SAML Administrator's Guide Product Release: 6.5 Date: July 05, 2018 esignlive 8200 Decarie Blvd, Suite 300 Montreal, Quebec H4P 2P5 Phone: 1-855-MYESIGN Fax: (514) 337-5258 Web: www.esignlive.com

More information

Using the VMware vcenter Orchestrator Client. vrealize Orchestrator 5.5.1

Using the VMware vcenter Orchestrator Client. vrealize Orchestrator 5.5.1 Using the VMware vcenter Orchestrator Client vrealize Orchestrator 5.5.1 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments

More information

VMware Identity Manager Administration

VMware Identity Manager Administration VMware Identity Manager Administration VMware Identity Manager 2.4 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

Setting Up Resources in VMware Identity Manager

Setting Up Resources in VMware Identity Manager Setting Up Resources in VMware Identity Manager VMware Identity Manager 2.7 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

ISA 767, Secure Electronic Commerce Xinwen Zhang, George Mason University

ISA 767, Secure Electronic Commerce Xinwen Zhang, George Mason University Identity Management and Federated ID (Liberty Alliance) ISA 767, Secure Electronic Commerce Xinwen Zhang, xzhang6@gmu.edu George Mason University Identity Identity is the fundamental concept of uniquely

More information

Configuring SAML-based Single Sign-on for Informatica Web Applications

Configuring SAML-based Single Sign-on for Informatica Web Applications Configuring SAML-based Single Sign-on for Informatica Web Applications Copyright Informatica LLC 2017. Informatica LLC. Informatica, the Informatica logo, Informatica Big Data Management, and Informatica

More information

edocs Home > BEA AquaLogic Service Bus 3.0 Documentation > Accessing ALDSP Data Services Through ALSB

edocs Home > BEA AquaLogic Service Bus 3.0 Documentation > Accessing ALDSP Data Services Through ALSB Accessing ALDSP 3.0 Data Services Through ALSB 3.0 edocs Home > BEA AquaLogic Service Bus 3.0 Documentation > Accessing ALDSP Data Services Through ALSB Introduction AquaLogic Data Services Platform can

More information

Using the VMware vrealize Orchestrator Client

Using the VMware vrealize Orchestrator Client Using the VMware vrealize Orchestrator Client vrealize Orchestrator 7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

Setting Up Resources in VMware Identity Manager. VMware Identity Manager 2.8

Setting Up Resources in VMware Identity Manager. VMware Identity Manager 2.8 Setting Up Resources in VMware Identity Manager VMware Identity Manager 2.8 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments

More information

API Security Management SENTINET

API Security Management SENTINET API Security Management SENTINET Overview 1 Contents Introduction... 2 Security Models... 2 Authentication... 2 Authorization... 3 Security Mediation and Translation... 5 Bidirectional Security Management...

More information

API Gateway. Version 7.5.1

API Gateway. Version 7.5.1 O A U T H U S E R G U I D E API Gateway Version 7.5.1 15 September 2017 Copyright 2017 Axway All rights reserved. This documentation describes the following Axway software: Axway API Gateway 7.5.1 No part

More information

Datapower is both a security appliance & can provide a firewall mechanism to get into Systems of Record

Datapower is both a security appliance & can provide a firewall mechanism to get into Systems of Record 1 2 3 Datapower is both a security appliance & can provide a firewall mechanism to get into Systems of Record 5 White boxes show the access points for different kinds of security. That s what we will

More information

Workspace ONE UEM Certificate Authentication for EAS with ADCS. VMware Workspace ONE UEM 1902

Workspace ONE UEM Certificate Authentication for EAS with ADCS. VMware Workspace ONE UEM 1902 Workspace ONE UEM Certificate Authentication for EAS with ADCS VMware Workspace ONE UEM 1902 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

Manufacturing Process Intelligence DELMIA Apriso 2017 Installation Guide

Manufacturing Process Intelligence DELMIA Apriso 2017 Installation Guide Manufacturing Process Intelligence DELMIA Apriso 2017 Installation Guide 2016 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA,

More information

Creating a REST API which exposes an existing SOAP Service with IBM API Management

Creating a REST API which exposes an existing SOAP Service with IBM API Management Creating a REST API which exposes an existing SOAP Service with IBM API Management 4.0.0.0 2015 Copyright IBM Corporation Page 1 of 33 TABLE OF CONTENTS OBJECTIVE...3 PREREQUISITES...3 CASE STUDY...4 USER

More information

Setting Up Resources in VMware Identity Manager (SaaS) Modified 15 SEP 2017 VMware Identity Manager

Setting Up Resources in VMware Identity Manager (SaaS) Modified 15 SEP 2017 VMware Identity Manager Setting Up Resources in VMware Identity Manager (SaaS) Modified 15 SEP 2017 VMware Identity Manager Setting Up Resources in VMware Identity Manager (SaaS) You can find the most up-to-date technical documentation

More information

Enforced Client Policy & Reporting Server (EPRS) 2.3. Administration Guide

Enforced Client Policy & Reporting Server (EPRS) 2.3. Administration Guide Enforced Client Policy & Reporting Server (EPRS) 2.3 Copyright 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell, the

More information

CA SiteMinder Web Services Security

CA SiteMinder Web Services Security CA SiteMinder Web Services Security Policy Configuration Guide 12.52 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation

More information

IBM Security Access Manager Version January Federation Administration topics IBM

IBM Security Access Manager Version January Federation Administration topics IBM IBM Security Access Manager Version 9.0.2.1 January 2017 Federation Administration topics IBM IBM Security Access Manager Version 9.0.2.1 January 2017 Federation Administration topics IBM ii IBM Security

More information

Oracle Cloud Using the Oracle Advanced Queuing (AQ) Adapter. Release 17.3

Oracle Cloud Using the Oracle Advanced Queuing (AQ) Adapter. Release 17.3 Oracle Cloud Using the Oracle Advanced Queuing (AQ) Adapter Release 17.3 E76448-04 September 2017 Oracle Cloud Using the Oracle Advanced Queuing (AQ) Adapter, Release 17.3 E76448-04 Copyright 2016, 2017,

More information

with Access Manager 51.1 What is Supported in This Release?

with Access Manager 51.1 What is Supported in This Release? 51 51 Integrating Microsoft SharePoint Server with Access Manager This chapter explains how to integrate Access Manager with a 10g WebGate and Microsoft SharePoint Server. It covers the following topics:

More information

Federated Identity Manager Business Gateway Version Configuration Guide GC

Federated Identity Manager Business Gateway Version Configuration Guide GC Tivoli Federated Identity Manager Business Gateway Version 6.2.1 Configuration Guide GC23-8614-00 Tivoli Federated Identity Manager Business Gateway Version 6.2.1 Configuration Guide GC23-8614-00 Note

More information

TIBCO Spotfire Automation Services 7.5. User s Manual

TIBCO Spotfire Automation Services 7.5. User s Manual TIBCO Spotfire Automation Services 7.5 User s Manual Revision date: 15 January 2016 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO

More information

Policy Manager for IBM WebSphere DataPower 7.2: Configuration Guide

Policy Manager for IBM WebSphere DataPower 7.2: Configuration Guide Policy Manager for IBM WebSphere DataPower 7.2: Configuration Guide Policy Manager for IBM WebSphere DataPower Configuration Guide SOAPMDP_Config_7.2.0 Copyright Copyright 2015 SOA Software, Inc. All rights

More information

Cloud Access Manager Overview

Cloud Access Manager Overview Cloud Access Manager 8.1.3 Overview Copyright 2017 One Identity LLC. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished

More information

Interoperability Solutions Guide for Oracle Web Services Manager 12c (12.2.1)

Interoperability Solutions Guide for Oracle Web Services Manager 12c (12.2.1) [1]Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager 12c (12.2.1) E57783-01 October 2015 Documentation for software developers that describes how to implement the

More information

Web Services DELMIA Apriso 2017 Implementation Guide

Web Services DELMIA Apriso 2017 Implementation Guide Web Services DELMIA Apriso 2017 Implementation Guide 2016 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA,

More information

Bomgar PA Integration with ServiceNow

Bomgar PA Integration with ServiceNow Bomgar PA Integration with ServiceNow 2017 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are the property of

More information

Cloud Access Manager Configuration Guide

Cloud Access Manager Configuration Guide Cloud Access Manager 8.1.3 Configuration Guide Copyright 2017 One Identity LLC. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide

More information

Security Assertions Markup Language (SAML)

Security Assertions Markup Language (SAML) Security Assertions Markup Language (SAML) The standard XML framework for secure information exchange Netegrity White Paper PUBLISHED: MAY 20, 2001 Copyright 2001 Netegrity, Inc. All Rights Reserved. Netegrity

More information

Oracle Cloud E

Oracle Cloud E Oracle Cloud Using the Evernote Adapter Release 16.3 E69234-05 September 2016 This guide describes how to configure and add the Evernote Adapter to an Oracle Integration Cloud Service integration. Oracle

More information

Installation and Upgrade Guide. Front Office v9.0

Installation and Upgrade Guide. Front Office v9.0 c Installation and Upgrade Guide Front Office v9.0 Contents 1.0 Introduction... 4 2.0 Prerequisites... 5 2.1 Database... 5 2.2 Portal and Web Service... 5 2.3 Windows Service... 5 3.0 New Installation...

More information

Sophos Mobile Control Network Access Control interface guide. Product version: 7

Sophos Mobile Control Network Access Control interface guide. Product version: 7 Sophos Mobile Control Network Access Control interface guide Product version: 7 Document date: January 2017 Contents 1 About this guide...3 2 About Sophos Mobile Control...4 3 Sophos Mobile Control NAC

More information

Configuring Funk Odyssey Software, Avaya AP-3 Access Point, and Avaya

Configuring Funk Odyssey Software, Avaya AP-3 Access Point, and Avaya Configuring Funk Odyssey Software, Avaya AP-3 Access Point, and Avaya 802.11a/b Wireless Client for User Authentication (802.1x) and Data Encryption - Issue 1.0 Abstract These Application Notes describe

More information

Oracle Cloud Using the Evernote Adapter. Release 17.3

Oracle Cloud Using the Evernote Adapter. Release 17.3 Oracle Cloud Using the Evernote Adapter Release 17.3 E69234-07 September 2017 Oracle Cloud Using the Evernote Adapter, Release 17.3 E69234-07 Copyright 2016, 2017, Oracle and/or its affiliates. All rights

More information

TIBCO ActiveMatrix Policy Director Administration

TIBCO ActiveMatrix Policy Director Administration TIBCO ActiveMatrix Policy Director Administration Software Release 2.0.0 November 2014 Document Updated: January 2015 Two-Second Advantage 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Interoperability Guide for Oracle Web Services Manager 11g Release 1 (11.1.1) E16098-01 October 2009 This document describes how to implement the most common Oracle WSM interoperability

More information

Five9 Plus Adapter for Agent Desktop Toolkit

Five9 Plus Adapter for Agent Desktop Toolkit Cloud Contact Center Software Five9 Plus Adapter for Agent Desktop Toolkit Administrator s Guide September 2017 The Five9 Plus Adapter for Agent Desktop Toolkit integrates the Five9 Cloud Contact Center

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Interoperability Guide for Oracle Web Services Manager 11g Release 1 (11.1.1) E16098-04 January 2011 This document describes how to implement the most common Oracle WSM interoperability

More information

DoD Common Access Card Authentication. Feature Description

DoD Common Access Card Authentication. Feature Description DoD Common Access Card Authentication Feature Description UPDATED: 20 June 2018 Copyright Notices Copyright 2002-2018 KEMP Technologies, Inc. All rights reserved. KEMP Technologies and the KEMP Technologies

More information

HPE Enterprise Integration Module for SAP Solution Manager 7.1

HPE Enterprise Integration Module for SAP Solution Manager 7.1 HPE Enterprise Integration Module for SAP Solution Manager 7.1 Software Version: 12.55 User Guide Document Release Date: August 2017 Software Release Date: August 2017 HPE Enterprise Integration Module

More information

Enabling SAML Authentication in an Informatica 10.2.x Domain

Enabling SAML Authentication in an Informatica 10.2.x Domain Enabling SAML Authentication in an Informatica 10.2.x Domain Copyright Informatica LLC 2017, 2018. Informatica, the Informatica logo, Informatica Big Data Management, and Informatica PowerCenter are trademarks

More information

Configuring Claims-based Authentication for Microsoft Dynamics CRM Server. Last updated: May 2015

Configuring Claims-based Authentication for Microsoft Dynamics CRM Server. Last updated: May 2015 Configuring Claims-based Authentication for Microsoft Dynamics CRM Server Last updated: May 2015 This document is provided "as-is". Information and views expressed in this document, including URL and other

More information

API Security Management with Sentinet SENTINET

API Security Management with Sentinet SENTINET API Security Management with Sentinet SENTINET Overview 1 Contents Introduction... 2 Security Mediation and Translation... 3 Security Models... 3 Authentication... 4 Authorization... 5 Bidirectional Security

More information

Neuron Change History

Neuron Change History Neuron 2.5.13.0 Change History The user can now create custom pipeline steps. The call web service step now has dynamic support for custom soap headers. New step to send and receive from Msmq New step

More information

Web Service Elements. Element Specifications for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 10.0(1) 1

Web Service Elements. Element Specifications for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 10.0(1) 1 Along with Action and Decision elements, another way to perform backend interactions and obtain real-time data is via the Web Service element. This element leverages industry standards, such as the Web

More information

Assignment 2. Start: 15 October 2010 End: 29 October 2010 VSWOT. Server. Spot1 Spot2 Spot3 Spot4. WS-* Spots

Assignment 2. Start: 15 October 2010 End: 29 October 2010 VSWOT. Server. Spot1 Spot2 Spot3 Spot4. WS-* Spots Assignment 2 Start: 15 October 2010 End: 29 October 2010 In this assignment you will learn to develop distributed Web applications, called Web Services 1, using two different paradigms: REST and WS-*.

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Using Oracle Eloqua Cloud Adapter Release 12.2.1.1.0 E73562-01 June 2016 Oracle Fusion Middleware Using Oracle Eloqua Cloud Adapter, Release 12.2.1.1.0 E73562-01 Copyright 2015,

More information

Minimum requirements for Portal (on-premise version):

Minimum requirements for Portal (on-premise version): Minimum requirements for Portal (on-premise version): Windows Server 2012 R2 Windows 10 (licensed) with the latest updates (64 bit only). All Windows applications must be licensed and activated. SQL Server

More information

SOA Software Policy Manager Agent v6.1 for tc Server Application Server Installation Guide

SOA Software Policy Manager Agent v6.1 for tc Server Application Server Installation Guide SOA Software Policy Manager Agent v6.1 for tc Server Application Server Installation Guide Trademarks SOA Software and the SOA Software logo are either trademarks or registered trademarks of SOA Software,

More information

Using the Horizon vrealize Orchestrator Plug-In

Using the Horizon vrealize Orchestrator Plug-In Using the Horizon vrealize Orchestrator Plug-In VMware Horizon 6 version 6.2.3, VMware Horizon 7 versions 7.0.3 and later Modified on 4 JAN 2018 VMware Horizon 7 7.4 You can find the most up-to-date technical

More information

SalesLogix Xbar User & Installation Guide

SalesLogix Xbar User & Installation Guide 1 Page SalesLogix Xbar Adm in Guide SalesLogix Xbar User & Installation Guide 2 Page SalesLogix Xbar Adm in Guide S T R A T E G I C S A L E S S Y S T E M S SalesLogix Xbar Our Mission Strategic Sales Systems

More information

Managing External Identity Sources

Managing External Identity Sources CHAPTER 5 The Cisco Identity Services Engine (Cisco ISE) integrates with external identity sources to validate credentials in user authentication functions, and to retrieve group information and other

More information

ForeScout Open Integration Module: Data Exchange Plugin

ForeScout Open Integration Module: Data Exchange Plugin ForeScout Open Integration Module: Data Exchange Plugin Version 3.2.0 Table of Contents About the Data Exchange Plugin... 4 Requirements... 4 CounterACT Software Requirements... 4 Connectivity Requirements...

More information

Concepts of Web Services Security

Concepts of Web Services Security Concepts of Web Services Security Session MCP/OS/MTP 4066 2:45 3:45pm, Halloween 2017 MGS, Inc. Software Engineering, Product & Services firm founded in 1986 Products and services to solve business problems:

More information

INSTALLATION GUIDE BIOVIA VAULT SERVER 2016

INSTALLATION GUIDE BIOVIA VAULT SERVER 2016 INSTALLATION GUIDE BIOVIA VAULT SERVER 2016 Copyright Notice 2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA,

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Using Oracle Eloqua Cloud Adapter Release 12.2.1.3.0 E83336-02 July 2017 Documentation for Oracle Service-Oriented Architecture (SOA) developers that describes how to use the Oracle

More information

DocuSign Single Sign On Implementation Guide Published: June 8, 2016

DocuSign Single Sign On Implementation Guide Published: June 8, 2016 DocuSign Single Sign On Implementation Guide Published: June 8, 2016 Copyright Copyright 2003-2016 DocuSign, Inc. All rights reserved. For information about DocuSign trademarks, copyrights and patents

More information

Single Sign-On for PCF. User's Guide

Single Sign-On for PCF. User's Guide Single Sign-On for PCF Version 1.2 User's Guide 2018 Pivotal Software, Inc. Table of Contents Table of Contents Single Sign-On Overview Installation Getting Started with Single Sign-On Manage Service Plans

More information

BMC FootPrints 12 Integration with Remote Support

BMC FootPrints 12 Integration with Remote Support BMC FootPrints 12 Integration with Remote Support 2003-2019 BeyondTrust Corporation. All Rights Reserved. BEYONDTRUST, its logo, and JUMP are trademarks of BeyondTrust Corporation. Other trademarks are

More information

Oracle Cloud Using the Oracle Responsys Adapter. Release 17.3

Oracle Cloud Using the Oracle Responsys Adapter. Release 17.3 Oracle Cloud Using the Oracle Responsys Adapter Release 17.3 E70393-06 September 2017 Oracle Cloud Using the Oracle Responsys Adapter, Release 17.3 E70393-06 Copyright 2016, 2017, Oracle and/or its affiliates.

More information

Hypertext Transfer Protocol Over Secure Sockets Layer (HTTPS)

Hypertext Transfer Protocol Over Secure Sockets Layer (HTTPS) Hypertext Transfer Protocol Over Secure Sockets Layer (HTTPS) This chapter provides information about Hypertext Transfer Protocol over Secure Sockets Layer. HTTPS, page 1 HTTPS for Cisco Unified IP Phone

More information

Oracle Cloud. Using Oracle Eloqua Adapter Release E

Oracle Cloud. Using Oracle Eloqua Adapter Release E Oracle Cloud Using Oracle Eloqua Adapter Release 12.1.3 E65434-01 August 2015 Oracle Cloud Using Oracle Eloqua Adapter, Release 12.1.3 E65434-01 Copyright 2015, Oracle and/or its affiliates. All rights

More information

Oracle Cloud Using the Trello Adapter. Release 17.3

Oracle Cloud Using the Trello Adapter. Release 17.3 Oracle Cloud Using the Trello Adapter Release 17.3 E84579-03 September 2017 Oracle Cloud Using the Trello Adapter, Release 17.3 E84579-03 Copyright 2016, 2017, Oracle and/or its affiliates. All rights

More information

TIBCO BusinessConnect SOAP Protocol Release Notes

TIBCO BusinessConnect SOAP Protocol Release Notes TIBCO BusinessConnect SOAP Protocol Release Notes Software Release 6.1.0 April 2015 Two-Second Advantage Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED

More information

McAfee Cloud Identity Manager

McAfee Cloud Identity Manager Marketo Cloud Connector Guide McAfee Cloud Identity Manager version 3.5 or later COPYRIGHT Copyright 2013 McAfee, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed,

More information

Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)

Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) CHAPTER 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) This chapter contains information on the following topics: HTTPS Overview, page 2-1 HTTPS for Cisco Unified IP Phone Services,

More information

Installation Guide - Mac

Installation Guide - Mac Kony Fabric Installation Guide - Mac On-Premises Release V8 Document Relevance and Accuracy This document is considered relevant to the Release stated on this title page and the document version stated

More information

Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)

Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) This chapter provides information about Hypertext Transfer Protocol over Secure Sockets Layer. HTTPS, page 1 HTTPS for Cisco Unified IP Phone

More information

OPC UA Configuration Manager PTC Inc. All Rights Reserved.

OPC UA Configuration Manager PTC Inc. All Rights Reserved. 2017 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 4 Overview 4 5 Project Properties - OPC UA 5 Server Endpoints 7 Trusted Clients 9 Discovery Servers 10 Trusted Servers 11 Instance

More information

Creating a REST API which exposes an existing SOAP Service with IBM API Management

Creating a REST API which exposes an existing SOAP Service with IBM API Management Creating a REST API which exposes an existing SOAP Service with IBM API Management 3.0.0.1 Page 1 of 29 TABLE OF CONTENTS OBJECTIVE...3 PREREQUISITES...3 CASE STUDY...3 USER ROLES...4 BEFORE YOU BEGIN...4

More information

TIBCO Spotfire Automation Services

TIBCO Spotfire Automation Services TIBCO Spotfire Automation Services Software Release 7.9 May 2017 Two-Second Advantage 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED

More information

Cisco VCS Authenticating Devices

Cisco VCS Authenticating Devices Cisco VCS Authenticating Devices Deployment Guide First Published: May 2011 Last Updated: November 2015 Cisco VCS X8.7 Cisco Systems, Inc. www.cisco.com 2 About Device Authentication Device authentication

More information

Oracle Fusion Middleware

Oracle Fusion Middleware Oracle Fusion Middleware Security and Administrator s Guide for Web Services 11g Release 1 (11.1.1) B32511-01 May 2009 This document describes how to administer and secure Web services using Enterprise

More information

User Manual. Admin Report Kit for IIS 7 (ARKIIS)

User Manual. Admin Report Kit for IIS 7 (ARKIIS) User Manual Admin Report Kit for IIS 7 (ARKIIS) Table of Contents 1 Admin Report Kit for IIS 7... 1 1.1 About ARKIIS... 1 1.2 Who can Use ARKIIS?... 1 1.3 System requirements... 2 1.4 Technical Support...

More information

SAML-Based SSO Configuration

SAML-Based SSO Configuration Prerequisites, page 1 SAML SSO Configuration Workflow, page 5 Reconfigure OpenAM SSO to SAML SSO After an Upgrade, page 9 Prerequisites NTP Setup In SAML SSO, Network Time Protocol (NTP) enables clock

More information

Configuring Alfresco Cloud with ADFS 3.0

Configuring Alfresco Cloud with ADFS 3.0 Configuring Alfresco Cloud with ADFS 3.0 Prerequisites: You have a working domain on your Windows Server 2012 and successfully installed ADFS. For these instructions, I created: alfresco.me as a domain

More information

Chapter 2 Introduction

Chapter 2 Introduction Chapter 2 Introduction PegaRULES Process Commander applications are designed to complement other systems and technologies that you already have in place for doing work. The Process Commander integration

More information