Security
- Security
- About this book
- Who this book is for
- What we need to know to understand this book
- Terms used in this book
- How to use this book
- Summary of changes
- Changes for this edition (plug-in version 6.0.2.11)
- Changes for the previous editions (SC34-6588-01 and SC34-6588-02)
- Introduction
- Security services
- Identification and authentication
- Access control
- Confidentiality
- Data integrity
- Non-repudiation
- Planning for your security requirements
- Basic considerations
- Authority to administer WebSphere MQ
- Authority to work with WebSphere MQ objects
- Channel security
- Additional considerations
- Queue manager clusters
- WebSphere MQ Publish/Subscribe
- WebSphere MQ internet pass-thru
- Link level security and application level security
- Link level security
- Application level security
- Comparing link level security and application level security
- Protecting messages in queues
- Queue managers not running in controlled and trusted environments
- Differences in cost
- Availability of components
- Messages in a dead letter queue
- What application level security cannot do
- Obtaining more information
- Cryptographic concepts
- Cryptography
- Message digests
- Digital signatures
- Digital certificates
- What is in a digital certificate
- Requirements for personal certificates
- Certification Authorities
- Distinguished Names
- How digital certificates work
- Obtaining personal certificates
- How certificate chains work
- When certificates are no longer valid
- Public Key Infrastructure (PKI)
- The Secure Sockets Layer (SSL)
- Transport Layer Security (TLS) concepts
- Secure Sockets Layer (SSL) concepts
- An overview of the SSL handshake
- How SSL provides authentication
- How SSL provides confidentiality
- How SSL provides integrity
- CipherSuites and CipherSpecs
- The Secure Sockets Layer in WebSphere MQ
- WebSphere MQ security provisions
- Access control
- Authority to administer WebSphere MQ
- Authority to administer WebSphere MQ on UNIX and Windows systems
- Authority to administer WebSphere MQ on i5/OS
- Authority to administer WebSphere MQ on z/OS
- Authority checks on z/OS
- Command security and command resource security
- MQSC commands and the system command input queue
- Access to the queue manager data sets
- Obtaining more information
- Authority to work with WebSphere MQ objects
- When authority checks are performed
- Alternate user authority
- Message context
- Authority to work with WebSphere MQ objects on i5/OS, UNIX systems, and Windows systems
- Distributed channels as queue manager objects
- Using PCF to access OAM commands
- Authority to work with WebSphere MQ objects on z/OS
- Channel security
- WebSphere MQ SSL support
- Channel attributes
- Channel status attributes
- Queue manager attributes
- The authentication information object (AUTHINFO)
- The SSL key repository
- Protecting WebSphere MQ client key repositories
- Refreshing a key repository
- Resetting SSL secret keys
- Federal Information Processing Standards (FIPS)
- WebSphere MQ client considerations
- Working with WebSphere MQ internet pass-thru (IPT)
- Support for cryptographic hardware
- Other link level security services
- Channel exit programs
- Security exit
- Message exit
- Send and receive exits
- Obtaining more information
- The SSPI channel exit program
- SNA LU 6.2 security services
- Session level cryptography
- Session level authentication
- Conversation level authentication
- Support for conversation level authentication in WebSphere MQ on i5/OS, UNIX systems, and Windows systems
- Conversation level authentication and WebSphere MQ for z/OS
- Obtaining more information
- Providing your own link level security
- Security exit
- Identification and authentication
- Access control
- MCAUserIdentifier
- WebSphere MQ Object Authority Manager user authentication
- Confidentiality
- Message exit
- Identification and authentication
- Access control
- Confidentiality
- Data integrity
- Non-repudiation
- Other uses of message exits
- Send and receive exits
- Confidentiality
- Data integrity
- Other uses of send and receive exits
- Access Manager for Business Integration
- Introduction
- Access control
- Identification and authentication
- Data integrity
- Confidentiality
- Non-repudiation
- Obtaining more information
- Providing your own application level security
- The API exit
- The API-crossing exit
- The role of the API exit and the API-crossing exit in security
- Identification and authentication
- Access control
- Confidentiality
- Data integrity
- Non-repudiation
- Other ways of providing your own application level security
- Working with WebSphere MQ SSL support
- Set up SSL communications
- Task 1: Using self-signed certificates
- The steps required to complete task 1
- 1. Prepare the key repository on each queue manager
- 2. Create a self-signed certificate for each queue manager
- 3. Add the self-signed certificate to the key repository
- 4. Extract a copy of each certificate
- 5. Exchange certificates
- 6. Add partner's certificate to the key repository
- 7. Define sender channel
- 8. Define a transmission queue
- 9. Define a receiver channel
- 10. Start the channel
- Result of task 1
- Verifying task 1
- Task 2: Using CA-signed certificates
- The steps required to complete task 2
- 1. Prepare the key repository on each queue manager
- 2. Request a CA-signed certificate for each queue manager
- 3. Add the Certification Authority's certificate to the key repository
- 4. Add the CA-signed certificate to the key repository
- 5. Define sender channel and associated transmission queue
- 6. Define receiver channel
- 7. Start the channel
- Result of task 2
- Verifying task 2
- Extensions to this task
- Task 3: Anonymous queue managers
- The steps required to complete task 3
- 1. Remove QMA’s personal certificate
- 2. Refresh the SSL environment (if necessary)
- 3. Allow anonymous connections on the receiver
- Result of task 3
- Verifying task 3
- Extensions to this task
- Working with the Secure Sockets Layer (SSL) on i5/OS
- Digital Certificate Manager (DCM)
- Accessing DCM
- Assigning a certificate to a queue manager
- Set up a key repository
- Creating a new certificate store
- Stashing the certificate store password
- Working with a key repository
- Locating the key repository for a queue manager
- Changing the key repository location for a queue manager
- When changes become effective
- Obtaining server certificates
- Creating CA certificates for testing
- Requesting a server certificate
- Adding server certificates to a key repository
- Managing digital certificates
- Transferring certificates
- Exporting a certificate from a key repository
- Importing a certificate into a key repository
- Removing certificates
- Configuring cryptographic hardware
- Mapping DNs to user IDs
- Working with the Secure Sockets Layer (SSL) on UNIX and Windows systems
- Using iKeyman, iKeycmd, and GSKCapiCmd
- Set up a key repository
- Accessing your key database file
- Accessing your key database file on Windows
- Accessing your key database file on UNIX
- Working with a key repository
- Locating the key repository for a queue manager
- Changing the key repository location for a queue manager
- Locating the key repository for a WebSphere MQ client
- Specifying the key repository location for a WebSphere MQ client
- When changes become effective
- Obtaining personal certificates
- Creating a self-signed personal certificate
- Requesting a personal certificate
- Receiving personal certificates into a key repository
- Managing digital certificates
- Transferring certificates
- Extracting a CA certificate from a key repository
- Extracting the CA part of a self-signed certificate from a key repository
- Adding a CA certificate (or the CA part of a self-signed certificate) into a key repository
- Exporting a personal certificate from a key repository
- Importing a personal certificate into a key repository
- Importing from a Microsoft .pfx file
- Importing from a PKCS #7 file
- Delete a personal certificate from a key repository
- Configuring for cryptographic hardware
- Managing certificates on PKCS #11 hardware
- Requesting a personal certificate for your PKCS #11 hardware
- Importing a personal certificate to your PKCS #11 hardware
- Mapping DNs to user IDs
- Migrating SSL security certificates in WebSphere MQ for Windows
- Working with the Secure Sockets Layer (SSL) on z/OS
- Set the SSLTASKS parameter
- Set up a key repository
- Ensuring CA certificates are available to a queue manager
- Working with a key repository
- Locating the key repository for a queue manager
- Specifying the key repository location for a queue manager
- Ensuring the CHINIT has the correct read access
- When changes become effective
- Obtaining personal certificates
- Creating a self-signed personal certificate
- Requesting a personal certificate
- Creating a RACF signed personal certificate
- Adding personal certificates to a key repository
- Managing digital certificates
- Transferring certificates
- Exporting a personal certificate from a key repository
- Importing a personal certificate into a key repository
- Removing certificates
- Delete a personal certificate from a key repository
- Renaming a personal certificate in a key repository
- Working with Certificate Name Filters (CNFs)
- Set up a CNF
- Working with Certificate Revocation Lists and Authority Revocation Lists
- Set up LDAP servers
- Configuring and updating LDAP servers
- Accessing CRLs and ARLs
- Accessing CRLs and ARLs with a queue manager
- Accessing CRLs and ARLs on i5/OS
- Accessing CRLs and ARLs using WebSphere MQ Explorer
- Accessing CRLs and ARLs with a WebSphere MQ client
- Accessing CRLs and ARLs with the Java client and JMS
- Checking CRLs and ARLs
- Manipulating authentication information objects with PCF commands
- Keeping CRLs and ARLs up to date
- Certificate validation and trust policy design on UNIX and Windows systems
- Basic certificate policy
- Basic CRL policy
- Basic path validation policy
- Standard policy (RFC-3280)
- Standard CRL policy
- Standard path validation policy
- Working with CipherSpecs
- Specifying CipherSpecs
- Obtaining information about CipherSpecs using WebSphere MQ Explorer
- Alternatives for specifying CipherSpecs
- Considerations for WebSphere MQ clusters
- Specifying a CipherSpec for a WebSphere MQ client
- Specifying a CipherSuite with the Java client and JMS
- Understanding CipherSpec mismatches
- WebSphere MQ rules for SSLPEER values
- Understanding authentication failures
- Cryptographic hardware
- Trademarks