Skip to content

Martini Configuration & Authentication for Consuming SOAP Services

Integrating with SOAP APIs involves specific steps for configuration and authentication to ensure secure and efficient communication between Martini and external SOAP services. This guide outlines how to configure SOAP service triggers in Martini and authenticate requests using supported mechanisms.

Configuration Steps

  1. WSDL Trigger Configuration

    • Obtain the WSDL URL of the SOAP service you wish to consume.
    • In Martini, navigate to the API integration settings and enter the WSDL URL. Martini will automatically parse the WSDL to identify available operations and the required SOAP actions.

  2. Service Configuration

    • Specify service details such as the SOAP trigger URLs for different environments (e.g., development, testing, production).
    • Configure necessary SOAP headers and namespaces as required by the SOAP service for correct request formatting.

Authentication Methods

Martini supports various authentication methods for SOAP APIs, ensuring compatibility with a wide range of security requirements:

  1. Basic Authentication

    • Suitable for SOAP services requiring a username and password.
    • Configure these credentials in Martini, which will then automatically add them to the SOAP header using the correct format.

  2. WS-Security

    • For SOAP services secured with WS-Security, Martini allows the configuration of security tokens, including UsernameToken and X.509 certificates.
    • Specify the necessary security token details in Martini to ensure they are included in the SOAP header for authenticated requests.

  3. OAuth

    • If the SOAP service is secured via OAuth, configure the OAuth details in Martini, including the client ID, client secret, and OAuth triggers.
    • Martini manages token acquisition and refresh, seamlessly integrating OAuth tokens into SOAP requests as required.

Securing SOAP API Consumption

To enhance security when consuming SOAP APIs, consider the following best practices:

  • Credentials Management: Store sensitive credentials securely in Martini's encrypted storage to protect them from unauthorized access.
  • HTTPS Triggers: Always use HTTPS for SOAP service triggers to encrypt data in transit, protecting it from interception or tampering.
  • Minimum Necessary Permissions: When configuring security settings, ensure only the minimum necessary permissions are granted for the operations your integration requires.

Testing and Validation

  • After setting up the SOAP service trigger and authentication in Martini:
    • Utilize Martini's built-in tools to test the SOAP service integration.
    • Send test requests to verify that the service responds correctly and that authentication is successfully processed.

This structured guide provides a clear pathway for developers to configure and authenticate SOAP API consumption in Martini, ensuring a secure and efficient integration process.