Security and high availability are two sides of the same coin for enterprise automation. In the latest IBM Workload Automation v10.2.6 release, we have introduced Centralized JWT Signing Key Management. This enhancement simplifies how security tokens are handled across your environment, especially in complex High Availability (HA) setups.
The Challenge: Token Consistency in HA
In previous versions, managing JSON Web Tokens (JWTs) often required manual synchronization or careful handling during certificate rotations. If a Master Domain Manager (MDM) failed over to a Backup MDM, ensuring that tokens remained valid across the shift was a critical step for business continuity.
The Solution: Database-Backed Key Storage
The signing key for JWTs is now centrally stored in the product database. This shift from local file-based storage to a centralized database model ensures that all components—regardless of where they are running—reference the same “source of truth” for token validation.
Key Features and Usage
- Proprietary Key Generation: The Master Domain Manager (MDM) now generates a proprietary key used specifically for signing certificates.
- Seamless Failover: Because the key is in the database, it is automatically shared between the Master and the Backup Master. If you need to switch managers, your security handshake remains intact.
- Persistence During Rotation: One of the biggest wins is that when you rotate your SSL certificates on the MDM, existing tokens remain valid. Since the signing key itself hasn’t changed, you avoid the “token expiration cliff” that often follows a security update.
- The mpjwtkey Alias: Your keystore now includes a certificate with the alias mpjwtkey. This contains the server public key (tls.crt). Note: This alias is critical for product functionality and should not be renamed or modified.
At a Glance: Benefits of Centralization
| Benefit | Impact |
| High Availability | Seamless token sharing between Master and Backup MDM. |
| Operational Stability | Signing keys are configured with a 100-year validity period. |
| Reduced Maintenance | Certificate rotation no longer invalidates active JWTs. |
| Uniformity | Ensures consistent token validation across all IWA components. |
Upgrade Considerations
Moving to 10.2.6 is designed to be “hands-off” regarding this change. If you are upgrading from a previous version:
- Automatic Management: The system automatically migrates the signing key location.
- No Manual Steps: There is no need for manual database injections or configuration file edits; the upgrade process preserves your security posture while enabling the new centralized logic.
Summary
By centralizing JWT signing keys, IBM Workload Automation 10.2.6 removes a layer of manual overhead for administrators. It ensures that your automation environment stays secure, consistent, and—most importantly—running, even during maintenance or failover events.
