Forward Proxy to support private key from B2Bi without SEAS

The existing feature currently supports fetching the private key only from LDAP, which is then used as the identity key when SSP initiates a connection to a remote partner. This enhancement request is to support a mechanism where the partner’s identity key (private key) can be fetched directly from B2Bi and passed through SSP Forward Proxy.

This capability would simplify migration scenarios where existing partner keys are already maintained in B2Bi, eliminating the need to duplicate or move them into LDAP. This would significantly reduce migration effort and complexity.

Additionally, this enhancement would remove the dependency on having SEAS as an extra infrastructure component solely for key retrieval. This would reduce:

• Additional infrastructure overhead of deploying and maintaining SEAS
• Extra configuration effort related to key management in SSP
• Overall solution complexity

This enhancement would be particularly beneficial in scenarios where:

• Customers are migrating from outbound B2Bi Perimeter Server to SSP Forward Proxy only
• Customers want to use SSP purely for Forward Proxy use cases without introducing SEAS into the architecture

We have already raised SSP2-I-224 for supporting key retrieval from B2Bi through SEAS. This new enhancement would complement that by providing another option where keys can be directly fetched from B2Bi without requiring SEAS, giving customers more flexibility depending on their architecture.