Securing

Image for this section Security tasks include setting up property extension databases and custom user repositories, configuring and activating SSL, and configuring authentication. In addition, tasks such as activating Federal Information Processing Standards (FIPS) security modules and configuring external security managers such as Tivoli® Access Manager might be required to secure your portal environment.

If you have not configured your user registry yet, go to the Installing section, select the appropriate operating system, and then choose the appropriate deployment scenario. Then select the Configuring portal to use a user registry topic.

Security and authentication considerations
Security and authentication are key elements of a production environment. Learn about single sign-on, credential vaults and external security managers.
Controlling access
After creating users and groups, you can assign them different levels of access to specific resources, roles, and policies. This access controls what actions they can perform on various pages, portlets, and applications.
Java 2 security with WebSphere Portal Express
Java 2 (J2SE) security provides a policy-based, fine-grain access control mechanism that increases overall system integrity by checking for permissions before allowing access to certain protected system resources. J2SE security allows you to set up individual policy files that control the privileges assigned to individual code sources. If the code does not have the required permissions and still tries to execute a protected operation, the Java Access Controller will throw a corresponding security exception.
Integrating with OpenID authentication
Web applications provide information and services to public users and personalized information and services to authenticated users. Users often work with multiple web applications, which require multiple IDs and passwords. This requirement can be difficult to maintain. Integrating identity providers (Google, Yahoo, or Facebook) into your site can simplify logging in for your users.
Enabling step-up authentication, the Remember me cookie, or both
Using step-up authentication and/or the Remember me cookie lets you fine-tune user authentication to pages and portlets.
Securing LTPA keys on a production environment
The Lightweight Third Party Authentication (LTPA) key holds cryptographic keys that secure the user authentication session and cookies. To secure the production server environment, regenerate the LTPA key using the WebSphere® Integrated Solutions Console. If you plan to enable single sign-on at a later time, you must first disable the automatic key generation.
Configuring SSL
Secure socket layers (SSL) encrypt traffic between the client browser and the server to secure information exchanged over the network between the browser and IBM® WebSphere Portal Express®. You will need to configure your environment for SSL to activate this additional security feature.
Enabling FIPS
IBM WebSphere Portal Express tolerates IBM WebSphere Application Server support of Federal Information Processing Standards (FIPS). You can configure WebSphere Application Server to activate FIPS 140-2 compliant security modules. When you enable FIPS, you can use only FIPS to securely encrypt data. For this reason, you must also configure FIPS for systems that require secure transactions, which can include HTTP servers and LDAP servers.
Configuring Session Security Integration
IBM WebSphere Application Server protects your session from access by other users.
Managing user data
Managing user data involves running configuration tasks to update or extend your user registry after the initial installation and deployment. Learn how to remove attributes that you need to update, add database user registries, configure property extension (lookaside) databases, and perform various other tasks to maintain your user registry.
Enabling HTTP Basic Authentication for simple clients
IBM WebSphere Portal Express provides an HTTP Basic Authentication Trust Association Interceptor that can be enabled to allow specific clients to log into the portal by using HTTP Basic Authentication instead of HTTP Form Based Authentication.
Setting up custom user repositories
A custom user repository is any repository that WebSphere Portal Express does not support out-of-box. However, you can configure WebSphere Portal Express to support any type of repository in a federated or stand-alone user registry, whether an LDAP directory, database, file system, and so on. Setting up custom user repositories involves tasks such as defining additional repositories to the default federated user registry, creating a custom stand-alone user repository, and updating your user repository to reflect changes in your environment. Learn what steps are required to create and update custom user repositories and what specific interfaces you must implement to enable communication between WebSphere Portal Express and a repository.
External security managers
Use external security managers such as IBM Tivoli Access Manager to perform authentication and authorization for IBM WebSphere Portal Express. You can use an external security manager for authentication only or for both authentication and authorization. Using an external security manager to perform only authorization is not supported at this time.
Deleting passwords from properties files
The configuration tasks might require you to write security-sensitive information, such as passwords, into multiple properties files. When you no longer need this security-sensitive information for your configuration, you should remove them and move the files to a safe place or set the file permissions so that only authorized users can read them.

Related concepts:

Installing

Related information:

WebSphere Application Server V7.0 Security Guide