WAS v8.5 > Secure applications and their environment
Secure the Liberty profile and its applications
This information applies to all types of application deployed on the Liberty profile. Security in the Liberty profile supports all the Servlet 3.0 security features and secured Java™ JMX connections. The following Liberty features are applicable to security in the Liberty profile:
- appSecurity-1.0 enables security for all web resources.
- ssl-1.0 enables SSL connections using HTTPS.
- restConnector-1.0 enables remote access by JMX client through a REST-based connector.
To learn about how security works in the Liberty profile, see Liberty profile: Security.
There are several security configuration examples under the /templates/config directory of the server image for reference when configuring security for your applications on the Liberty profile.
Best practice: When you use the developer tools to configure the security on the Liberty profile, make sure the configuration created by the tools is similar to the examples in the ${wlp.install.dir}/templates/config directory of the server image. This directory includes examples of configuring some of the most common security features. If we see any differences in the configuration created by the developer tools and the examples, modify the configuration to fit the configuration in the examples for that feature.
See also
- Getting started with security in the Liberty profile
We can use the quickStartSecurity element to quickly enable a simple (one user) security setup for the Liberty profile.- Secure communications with the Liberty profile
We can configure the Liberty profile server to provide secure communications between a client and the server.- Authenticate users in the Liberty profile
The Liberty profile server uses a user registry to authenticate a user and retrieve information about users and groups to perform security-related operations, including authentication and authorization.- Authorizing access to resources in the Liberty profile
The purpose of authorization is to determine whether a user or group has the necessary privileges to access a resource.- Configuring secure JMX connection to the Liberty profile
This topic describes how to access the secured Java Management Extensions (JMX) connectors on the Liberty profile using SSL.- Configuring web security related properties for the Liberty profile
We can configure web security related properties for the Liberty profile, such as SSO and client certificate authentication.- Configure authentication aliases for the Liberty profile
We can configure an authentication data alias to use with a resource reference for authentication on the Liberty profile.- Developing extensions to the Liberty profile security infrastructure
The Liberty profile server provides various plug points so that we can extend the security infrastructure.
Parent topic: Using the Liberty profile as an application development environment
Related concepts:
|