Mule

SSL Transport provider

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-rc2
  • Fix Version/s: 1.0-rc3
  • Component/s: Core: Transports
  • Labels:
    None
  • Similar Issues:
    MULE-1660 XMPP over SSL
    MULE-4064 transport archetype does not provide option to not extend any existing transport
    MULE-172 RMI provider
    MULE-864 Mx4j + SSL does not work under IBM JDK
    MULE-563 A transport provider for interacting with Spaces
    MULE-165 Writ e a Guide for developing custom Transport providers
    MULE-173 Add Corba IIOP transport provider
    MULE-566 Add Axis2 transport provider
    MULE-849 m2: running Http and SSL providers' tests from the project root produces a certificate error
    MULE-862 SSL provider does not compile/run under IBM JDK/WebSphere

Description

This should be trivial to implement on top of the Tcp provider and could enable MULE-63 (Https) support.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment - 25/Feb/05 10:24 AM

Can now enable ssl connections using ssl://localhost:3333 or using tls tls://localhost:4444
Note that you need to configure the connector with keystore ans certificate info. se the Transports Guide for more info.

Show
Ross Mason added a comment - 25/Feb/05 10:24 AM Can now enable ssl connections using ssl://localhost:3333 or using tls tls://localhost:4444 Note that you need to configure the connector with keystore ans certificate info. se the Transports Guide for more info.

People

Vote (0)
Watch (0)

Dates

  • Created:
    12/Feb/05 10:25 PM
    Updated:
    21/Aug/06 09:23 PM
    Resolved:
    25/Feb/05 10:24 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.