Book description
What do you think of when someone mentions z/OS security? Probably of something that is trustworthy, or even impenetrable. Perhaps you also think of something that is a little complex and challenging to administer.
What comes to mind when someone mentions Internet security? Perhaps you think of prominent Web sites that have been maliciously "hacked" or credit card numbers that have been stolen.
Using working examples of code and configuration files, in this IBM Redbooks publication, we explain how you can run your Web-enabled applications with as high a level of security as other z/OS applications and subsystems, even if those applications were written or originally deployed on another platform, by using the Java 2 Platform Enterprise Edition (J2EE) programming model and IBM WebSphere Application Server for z/OS and OS/390.
This book will help architects, application programmers, WebSphere and security administrators, and application and network architects to understand and use these products.
Please note that the additional material referenced in the text is not available from IBM.
Table of contents
- Notices
- Preface
- Summary of changes
-
Part 1: Introduction to WebSphere and J2EE security
-
Chapter 1: WebSphere Application Server V5 security overview
- WebSphere Application Server for z/OS Version 5 infrastructure overview and terminology
- WebSphere Application Server V5 security features
- J2EE 1.3 compliance features
- WebSphere Network Deployment family compliance features at interface layer
- Support of WebSphere family security configurations
- J2EE 1.3-compliant security enhancements (1/2)
-
J2EE 1.3-compliant security enhancements (2/2)
- Java 2 security
- J2EE role-based authorization enhancements
- WebSphere Application Server V5 and JAAS
- Java 2 security, J2EE security, and JAAS feature comparison
- z/OS Java security components
- JSSE security
- CSIv2 security protocol
- Pluggable authentication security
- Security configuration in z/OS and OS/390
- Enabling global security
- Comparisons between WebSphere Application Server for z/OS and OS/390 V4.0.1 and V5
- Key differences between WebSphere Application Server for z/OS and distributed platforms
- Summary
- Chapter 2: Security design
-
Chapter 3: J2EE 1.3 and WebSphere Application Server V5 security concepts
- Overview
- J2EE container-based security (1/3)
- J2EE container-based security (2/3)
- J2EE container-based security (3/3)
- Resource authentication
- Security interoperability using IIOP
- Additional security capabilities (1/4)
- Additional security capabilities (2/4)
- Additional security capabilities (3/4)
- Additional security capabilities (4/4)
- Chapter 4: WebSphere Application Server application security
-
Chapter 5: WebSphere application migration security aspects
- Application migration security aspect checklist
- Application migration strategies
- Migrating IBM HTTP Server thread level-based security
- Migrating WebSphere Application Server thread level-based security
- Security aspects when migrating Common Connector Framework (CCF) connectors
- Security aspects when migrating J2CA connectors
- Migrating SOMDOBJS to EJBROLE (1/2)
- Migrating SOMDOBJS to EJBROLE (2/2)
-
Chapter 1: WebSphere Application Server V5 security overview
-
Part 2: SWIPE and our testing infrastructure
-
Chapter 6: The sandbox infrastructure
- Physical integration into the network infrastructure
- System setup and service levels
- Naming conventions (1/2)
-
Naming conventions (2/2)
- WebSphere cells
- Naming convention variables
- Data sets and files
- Component trace procedure names
- Configuration objects
- Development base servers started tasks and user IDs
- Deployment manager started tasks and user IDs
- Node agent started tasks and user IDs
- Managed servers started tasks and user IDs
- TCP/IP ports
- Common information
- Starting servers
-
Chapter 7: The security investigation application
- The SWIPE application (1/2)
- The SWIPE application (2/2)
- SWIPE authentication features
- Authorization features (1/4)
- Authorization features (2/4)
- Authorization features (3/4)
- Authorization features (4/4)
- The downloadable SWIPE package
- Deploying SWIPE
- SWIPE: Running EJBCaller (1/3)
- SWIPE: Running EJBCaller (2/3)
- SWIPE: Running EJBCaller (3/3)
- RACF definitions (1/2)
- RACF definitions (2/2)
-
Chapter 8: The security investigation applications for EIS
- The SWIPE application for CICS, IMS, and DB2 (1/3)
- The SWIPE application for CICS, IMS, and DB2 (2/3)
- The SWIPE application for CICS, IMS, and DB2 (3/3)
- Define J2CA connection factories and data sources (1/2)
- Define J2CA connection factories and data sources (2/2)
- Install SWIPE for CICS, IMS, and DB2
- Install the CICS components of SWIPECICS
- Start SWIPE for CICS, IMS, and DB2
- Run SWIPE for CICS, IMS, and DB2
- Debug SWIPE for CICS, IMS, and DB2
- The SWIPE application for JMS (1/3)
- The SWIPE application for JMS (2/3)
-
The SWIPE application for JMS (3/3)
- Invoke the JMS sample
- SWIPE application for JMS contents
- Security roles in the samples
- WebSphere MQ
- Prepare WebSphere security to run the samples
- WebSphere MQ: Queue definitions
- WebSphere MQ: RACF resource profiles
- J2C authentication data entries
- JMS queue connection factory definitions
- Queue destination definitions
- SWIPE JMS: Logical resources
- Install the SWIPE JMS application
- Run the SWIPE JMS application
- RACF messages
- Check the user ID that flows to WebSphere MQ
-
Chapter 6: The sandbox infrastructure
-
Part 3: Cryptography
-
Chapter 9: Using cryptographic services
- Cryptographic support
- How WebSphere fits in z/OS and zSeries cryptographic infrastructure
- Hardware cryptography support for zSeries 2084 or 2086 engines
- Activation of hardware cryptography support for zSeries 2084, 2086, 9672, 2064, 2066, or 7060 engines (1/3)
- Activation of hardware cryptography support for zSeries 2084, 2086, 9672, 2064, 2066, or 7060 engines (2/3)
-
Activation of hardware cryptography support for zSeries 2084, 2086, 9672, 2064, 2066, or 7060 engines (3/3)
- Verify that your processor has Cryptographic Coprocessor
- Obtain the correct configuration enablement diskette or diskettes for your processor
- Load the configuration enablement diskette(s)
- Assign Cryptographic Coprocessors to LPARs
- Additional instruction for assigning the PCI crypto features to LPARs with a 2084 or 2086 engine
- Install and initialize Integrated Cryptographic Service Facility
- Initialize the CKDS and PKDS and load your master key
- Configure WebSphere to use hardware cryptographic services
- Securing and maintaining cryptography
- Create RACF keyrings and certificates
- Set up Secure Sockets Layer (SSL) for WebSphere for z/OS (1/5)
- Set up Secure Sockets Layer (SSL) for WebSphere for z/OS (2/5)
- Set up Secure Sockets Layer (SSL) for WebSphere for z/OS (3/5)
- Set up Secure Sockets Layer (SSL) for WebSphere for z/OS (4/5)
-
Set up Secure Sockets Layer (SSL) for WebSphere for z/OS (5/5)
- Certificates in WebSphere and RACF
- SSL client certificate security for your WebSphere Application Server and clients
- Define SSL security for servers and clients
- Use certificates to set up HTTPS internal transport connections
- Set up secure HTTPS internal transport connections using a server certificate signed by an internal CA
- Set up secure HTTPS internal transport connections using client certificates signed by an internal CA
- Set up secure HTTPS internal transport connections using server certificates signed by an external CA
- Set up secure HTTPS internal transport connections using client certificates signed by an external CA
-
Chapter 9: Using cryptographic services
-
Part 4: WebSphere Application Server for z/OS security infrastructure
-
Chapter 10: WebSphere Application Server runtime security
- WebSphere address space concepts
- WebSphere Application Server SAF integration
- Basic RACF setup for z/OS
- SAF naming standards and conventions
- Setting up RACF controls for products related to WebSphere
- RACF protection for LDAP servers on z/OS
- RACF protection for DB2
- RACF protection for IBM HTTP Server for z/OS
- Summary of RACF general resource classes used by WebSphere
- The WebSphere ISPF installation security dialog (1/3)
- The WebSphere ISPF installation security dialog (2/3)
-
The WebSphere ISPF installation security dialog (3/3)
- Security Customization panel settings
- ISPF customization dialogs for RACF command generation
- RACF definitions, naming conventions, and considerations for WebSphere environments on z/OS
- Define RACF groups for WebSphere
- Define RACF user IDs for the WebSphere infrastructure
- Protect WebSphere-related data sets with RACF
- Profiles for WebSphere in class STARTED
- Profiles for WebSphere in class LOGSTRM
- Profiles for WebSphere in class CBIND
- Profiles for WebSphere in class SERVER
- Profiles in class REALM
- HFS security
- HFS ACLs (1/2)
- HFS ACLs (2/2)
- zFS security
- Chapter 11: Registries
- Chapter 12: Local operating system registries
-
Chapter 13: Remote registries
- Remote or pluggable registries for WebSphere
- The concept of identity mapping
- Trust association interceptor
- How to interact with a remote registry
- Sample scenario: Using LDAP native authentication (1/5)
- Sample scenario: Using LDAP native authentication (2/5)
- Sample scenario: Using LDAP native authentication (3/5)
- Sample scenario: Using LDAP native authentication (4/5)
- Sample scenario: Using LDAP native authentication (5/5)
- Sample scenario: Authentication with Tivoli Access Manager for e-business WebSEAL (1/2)
- Sample scenario: Authentication with Tivoli Access Manager for e-business WebSEAL (2/2)
- Sample scenario: Implementing file-based custom user registry
- Sample scenario: Off-platform authentication with WebSEAL on Linux for zSeries using TAI
- Sample scenario: Implementing a custom TAI
- Registry choices summary table
-
Chapter 14: IBM Tivoli Access Manager and WebSphere Application Server integration
- Introducing IBM Tivoli Access Manager for WebSphere (1/2)
-
Introducing IBM Tivoli Access Manager for WebSphere (2/2)
- Tivoli Access Manager features and components
- Why use Tivoli Access Manager with WebSphere?
- Scenario 1: Tivoli Access Manager authentication and LocalOS authorization for WebSphere
- Scenario 2: Tivoli Access Manager authentication and authorization for WebSphere
- Scenario 3: Tivoli Access Manager authentication, authorization, and native authentication for WebSphere
- Configuring Tivoli Access Manager and WebSphere Application Server integration (1/7)
- Configuring Tivoli Access Manager and WebSphere Application Server integration (2/7)
- Configuring Tivoli Access Manager and WebSphere Application Server integration (3/7)
- Configuring Tivoli Access Manager and WebSphere Application Server integration (4/7)
- Configuring Tivoli Access Manager and WebSphere Application Server integration (5/7)
- Configuring Tivoli Access Manager and WebSphere Application Server integration (6/7)
-
Configuring Tivoli Access Manager and WebSphere Application Server integration (7/7)
- Tivoli Access Manager setup in our environment
- Configure Tivoli Access Manager for WebSphere
- Configure WebSphere for Tivoli Access Manager
- Enable WebSphere Application Server security to use Tivoli Access Manager
- Migrate WebSphere Application Server security settings
- Configure single sign-on between WebSEAL and WebSphere
- Using Tivoli Access Manager for WebSphere (1/3)
- Using Tivoli Access Manager for WebSphere (2/3)
- Using Tivoli Access Manager for WebSphere (3/3)
-
Chapter 15: WebSphere administration and administrative security
- WebSphere administration approaches
- Securing the administrative tasks
- Securing JMX and MBeans
- WebSphere administration authentication
- Role-based administrative security
- Fencing servers, nodes, and cells in a sysplex
- Enabling global security (1/2)
- Enabling global security (2/2)
- Securing the CosNaming service
-
Chapter 16: Web container security
- Introduction
- Web container authentication (1/8)
- Web container authentication (2/8)
- Web container authentication (3/8)
- Web container authentication (4/8)
- Web container authentication (5/8)
- Web container authentication (6/8)
- Web container authentication (7/8)
- Web container authentication (8/8)
- Web container authorization (1/3)
- Web container authorization (2/3)
- Web container authorization (3/3)
- Web container identity delegation and propagation
-
Chapter 17: Security integration with the WebSphere HTTP plug-in
- Multi-tier topologies and DMZ (1/2)
- Multi-tier topologies and DMZ (2/2)
- WebSphere and HTTP server plug-ins
- WebSphere HTTP plug-in description (1/3)
- WebSphere HTTP plug-in description (2/3)
-
WebSphere HTTP plug-in description (3/3)
- WebSphere HTTP plug-in configuration
- WebSphere HTTP plug-in execution flow
- Defining virtual hosts and HTTP transports
- WebSphere HTTP plug-in configuration file generation
- IBM HTTP Server for WebSphere Application Server for z/OS HTTP plug-in configuration
- Distributed HTTP server WebSphere HTTP plug-in configuration
- Protection setups in the IBM HTTP Server and security credential forwarding
- SSL authentication with the WebSphere HTTP plug-in (1/2)
- SSL authentication with the WebSphere HTTP plug-in (2/2)
- Validation tests for IBM HTTP Server for z/OS
- WebSphere HTTP plug-in on distributed platforms (1/2)
- WebSphere HTTP plug-in on distributed platforms (2/2)
- Security validation for the WebSphere HTTP plug-in on distributed platforms: Test cases
-
Chapter 18: EJB container security
- EJB container authentication protocols
- Common Secure Interoperability Version 2 (CSIv2) (1/3)
- Common Secure Interoperability Version 2 (CSIv2) (2/3)
- Common Secure Interoperability Version 2 (CSIv2) (3/3)
- CSIv2 solution scenarios (1/2)
- CSIv2 solution scenarios (2/2)
- zSAS authentication protocol (1/4)
- zSAS authentication protocol (2/4)
- zSAS authentication protocol (3/4)
- zSAS authentication protocol (4/4)
- EJB container authorization
- Security propagation
- EJB container security verification using SWIPE
- CSIv2 security verification using SWIPE (1/2)
- CSIv2 security verification using SWIPE (2/2)
- Chapter 19: WebSphere Application Server logging and auditing
- Chapter 20: Web services security
-
Chapter 10: WebSphere Application Server runtime security
-
Part 5: Appendixes
-
Appendix A: Setup and debugging guides
- Configuring SSL between WebSphere Application Server and a CICS Transaction Gateway daemon
- Detailed steps for using gsskyman (1/2)
- Detailed steps for using gsskyman (2/2)
- Using keytool to drive iKeyman
- Using iKeyman on Windows
- Importing WebSphere’s certificate in CICS Transaction Gateway KDB
- Creating a connection factory to support SSL
- Certificate generation hints for network deployment cells
- Troubleshooting ICSF Pass Phrase initialization problems
- LDAP activity logging
- Tracing System SSL
- Appendix B: Additional material
-
Appendix A: Setup and debugging guides
- Related publications
- Index (1/5)
- Index (2/5)
- Index (3/5)
- Index (4/5)
- Index (5/5)
- Back cover
Product information
- Title: WebSphere Application Server for z/OS V5 and J2EE 1.3 Security Handbook
- Author(s):
- Release date: June 2005
- Publisher(s): IBM Redbooks
- ISBN: None
You might also like
book
Low-Code Application Development with Appian
Go from no-code to low-code and translate your business requirements into full-fledged enterprise-ready applications Key Features …
audiobook
How to Do Nothing
A galvanizing critique of the forces vying for our attention-and our personal information-that redefines what we …
video
Java SE 17 Developer (1Z0-829)
21+ Hours of Video Instruction An intensive and guided video course to learn and practice while …
book
Modern Software Engineering: Doing What Works to Build Better Software Faster
Improve Your Creativity, Effectiveness, and Ultimately, Your Code In Modern Software Engineering, continuous delivery pioneer David …