Thank you for the suggestion.
This is a possibility, would prefer not to change out-of-the-box BPs.
I tried to find a way to use a custom PGP Package BP, but that does not seem to be configurable.
Seems the issue is really more with the Routing Service. setting the routing activity to failure since consumer is not set up.
May try to set up 2 (or 3?) dynamic routing channel templates - pgp encrypt and sign, pgp encrypt, no encrypt - and use for most partners
If the consuminlg partner is set up to encrypt and sign, then the first routing channel would work, and "hopefully" the "other' routing channels would not be attempted
If the consuming partner is NOT set up to encrypt and sign, then the first routing channel would fail, and then the encrypt only routing channel would be attempted, if the consuming partner was set up for encryption only, then the routing would succeed, and "hopefully" the no encrypt routing channel would not be attempted
If the partner is set up not to encrypt, then the 3rd routing channel would be used and should be successful.
This too seems "convoluted" even if it did work ... but may be worth it. At least it would separate the consumer pgp preference from being "in sync" with the routing channel.
just rambling . . .
------------------------------
Vincent Miller
------------------------------
Original Message:
Sent: Fri May 08, 2020 11:29 AM
From: Rajasekhar Muthamsetty
Subject: SFG - How can SFG be configured to base PGP Encryption on Consuming Partner configuration?
If you have not already considered or tried, try this once.
- Create RCT with no Encryption.
- Edit FileGatewaySendMessage BP to query the TP profile (or custom reference table) to check if PGP and/or Signing required, and proceed.
IBM advises to not edit these FG predefined BP's, But I believe this change can be done with precaution by keeping it's required inputs as is.
------------------------------
Rajasekhar Muthamsetty
Original Message:
Sent: Tue May 05, 2020 03:40 PM
From: Vincent Miller
Subject: SFG - How can SFG be configured to base PGP Encryption on Consuming Partner configuration?
Rajasekhar Muthamsetty,
Thank you for responding.
Yes, we are aware we can address this with custom protocols.
However, this means we would have to build custom protocols for all the protocols we use whose partners use PGP Encryption.
We would also not be able to use the pgp package and unpackaged layers in the routing channel templates.
This just seems like something that should be able to be done within the existing framework.
And certain document references seem to imply it can be done.
------------------------------
Vincent Miller
Original Message:
Sent: Tue May 05, 2020 11:15 AM
From: Rajasekhar Muthamsetty
Subject: SFG - How can SFG be configured to base PGP Encryption on Consuming Partner configuration?
Did you consider using a custom protocol to control plain, encryption and encryption with signing, and the file name extensions?
------------------------------
Rajasekhar Muthamsetty
Original Message:
Sent: Mon May 04, 2020 08:44 PM
From: Vincent Miller
Subject: SFG - How can SFG be configured to base PGP Encryption on Consuming Partner configuration?
We have thousands of consuming partners configured.
- Some with no PGP encryption required.
- Some with PGP Encryption required.
- Some with PGP Encryption and signing required.
And often these requirements change.
The routing channel configuration becomes cumbersome when for each type of flow
- 3 separate routing channel templates are needed for each type of flow
- Each customer must be assigned to the proper routing channel template (or put in a specific partner group which uses the specific RCT)
We also would prefer to use more dynamic routing templates, but again would prefer not them not to be tied to PGP Encryption (unencrypted, encrypted or encrypted and signed)
Is there a way to have SFG handle PGP Encryption based on the consumer PGP Config instead of being based on the RCT?
Having 3 dynamic RCTs would even be OK, if the result would be 1 and only only 1 document would be sent to the consumer in the PGP format defined in the Consuming Partner.
The fact that the ConsumerPgpExtension value may be:
- .pgp - consumer prefers a PGP file
- .asc - consumer prefers an ASCII encoded pgp file
- (blank) - consumer does not prefer a PGP file
Seems to hint that PGP encryption can somehow be based on the Consuming Partner PGP Configuration
Any recommendations would be appreciated.
------------------------------
Vincent Miller
------------------------------
#filetransfer
#DataExchange