Jakarta Connectors 2.0 Inbound Security

This feature enables security inflow for resource adapters. This is the final release of this feature and is only compatible with Jakarta EE 9. For Jakarta EE 10, the same functionality is automatically enabled when the connectors and appSecurity features are enabled.

Enable this feature

To enable the Jakarta Connectors 2.0 Inbound Security feature, add the following element declaration into server.xml, inside the featureManager element:

<feature>connectorsInboundSecurity-2.0</feature>

Feature configuration elements

• administrator-role
• authCache
• authData
• authentication
• basicRegistry
• cache
• cacheManager
• cachingProvider
• classloader
• classloading
• jaasLoginContextEntry
• jaasLoginModule
• kerberos
• library
• ltpa
• quickStartSecurity
• reader-role
• transaction
• trustAssociation

Standard API packages provided by this feature

• jakarta.security.auth.message.callback

Liberty API packages provided by this feature

• com.ibm.websphere.security.auth.callback
• com.ibm.wsspi.security.auth.callback
• com.ibm.wsspi.security.common.auth.module
• com.ibm.wsspi.security.tai
• com.ibm.wsspi.security.token

Features that this feature enables

• connectors-2.0
• ssl-1.0

Supported Java versions

• JavaSE-1.8
• JavaSE-11.0
• JavaSE-17.0
• JavaSE-21.0
• JavaSE-24.0

Platform Versions

• jakartaee-9.1

Features that enable this feature

• jakartaee-9.1

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.

io.openliberty.connectorsInboundSecurity-2.0; type="osgi.subsystem.feature"