Secure Socket Layer 1.0
This feature enables support for Secure Sockets Layer (SSL) connections. The secure HTTPS listener is not started unless the ssl-1.0 feature is enabled and a keystore is configured.
Enable this feature
To enable the Secure Socket Layer 1.0 feature, add the following element declaration into the server.xml file, inside the featureManager element:
<feature>ssl-1.0</feature>
Features that this feature is superseded by
Feature configuration elements
Liberty API packages provided by this feature
- com.ibm.websphere.endpoint
- com.ibm.websphere.ssl
Supported Java versions
- JavaSE-1.8
- JavaSE-11.0
- JavaSE-17.0
- JavaSE-21.0
- JavaSE-24.0
Features that enable this feature
- acmeCA-2.0
- adminCenter-1.0
- apiDiscovery-1.0
- appSecurity-2.0
- appSecurity-3.0
- appSecurity-4.0
- appSecurity-5.0
- appSecurityClient-1.0
- audit-1.0
- audit-2.0
- batchManagement-1.0
- collectiveController-1.0
- connectorsInboundSecurity-2.0
- federatedRegistry-1.0
- jcaInboundSecurity-1.0
- jwt-1.0
- logstashCollector-1.0
- messagingSecurity-3.0
- mpMetrics-1.0
- mpMetrics-1.1
- mpMetrics-2.0
- mpMetrics-2.2
- mpMetrics-2.3
- mpMetrics-3.0
- mpMetrics-4.0
- mpMetrics-5.0
- mpMetrics-5.1
- oauth-2.0
- openapi-3.0
- openapi-3.1
- productInsights-1.0
- restConnector-1.0
- restConnector-2.0
- samlWeb-2.0
- scim-1.0
- transportSecurity-1.0
- usageMetering-1.0
- wasJmsSecurity-1.0
- wsAtomicTransaction-1.2
Develop a feature that depends on this feature
If we are developing a feature that depends on this feature, include the following item in the Subsystem-Content header in your feature manifest file.
com.ibm.websphere.appserver.ssl-1.0; type="osgi.subsystem.feature"
SPI packages provided by this feature
- com.ibm.wsspi.ssl