Jakarta Authentication
3.0
2.0
1.1

This feature enables support for securing the server runtime environment and applications using Jakarta Authentication 2.0 providers

If you are updating your application from using the appAuthentication-2.0 feature to using the appAuthentication-3.0 feature, changes in API behavior might require you to update your application code. For more information, see Differences between Jakarta Authentication 3.0 and 2.0.

Enabling this feature

To enable the Jakarta Authentication 2.0 feature, add the following element declaration into your server.xml file, inside the featureManager element:

<feature>appAuthentication-2.0</feature>

Standard API packages provided by this feature

  • jakarta.security.auth.message

  • jakarta.security.auth.message.callback

  • jakarta.security.auth.message.config

  • jakarta.security.auth.message.module

Features that this feature enables

Supported Java versions

  • JavaSE-1.8

  • JavaSE-11.0

  • JavaSE-17.0

  • JavaSE-20.0

Features that enable this feature

Developing a feature that depends on this feature

If you 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.appAuthentication-2.0; type="osgi.subsystem.feature"

SPI packages provided by this feature

  • com.ibm.wsspi.security.jaspi