Native PGP, introduced in IBM Sterling B2B Integrator 6.1, performs PGP encryption, decryption, signing and verification inside the product and manages keys through the PGP Key Management dashboard and REST APIs. IBM's migration guidance states that when partner public keys are checked in, their Key IDs are stored as 16-bit IDs. Existing Sterling File Gateway trading partner profiles and PGP business processes that were built for external PGP often hold the shorter 8-bit key ID. IBM therefore recommends replacing those values with the 16-bit key ID, which is visible under Trading Partner > PGP Public Key in the dashboard. For example, the public_user value in the PGPPackageService business process should be updated, and consumer partners should be configured with the last 16 digits of the key fingerprint. In IBM's terminology the 16-bit label refers to the long key identifier of sixteen hexadecimal characters, as opposed to the short eight-character form. An 8-bit ID is the legacy format that must be migrated, and the 32-bit and 64-bit options are not the lengths documented for Native PGP in this context.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit