Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Enhancement to PGP Xprocessor functionality
Currently, The PGP XProcessor requires the following fields as input. The XProcessor Driver will look up the fields using the Profile Name and pass that data to the Utility class.
Fields for Both Inbound and Outbound
The following fields are required for Inbound and Outbound PGP:
Managed Customer PGP Key (public and private)
Trading Partner PGP Key (public only)
Additional Fields for Inbound Only
The following field is required for Inbound PGP only:
Require Signed Data? (Yes, No)
Additional Fields for Outbound Only
The following fields are required for Outbound PGP only:
Sign? (Yes, No)
Encrypt? (Yes, No)
Compress? (Yes, No)
ASCII Armor? (Yes, No)
The implementer needs to use rule assignments to provide these fields to the XProcessor Driver.
Action:
Encrypt
Decrypt
An implementer cannot setup an PGP Xprocessor without an Action.
My request is to add additional functionality to be able to just Sign ONLY an Inbound/outbound document without having to use Action: Encrypt or Decrypt
|
What is your industry?
|
Electronics
|
|
How will this idea be used?
Requirement :
Step 1 :For all inbound invoices IBM to first copy the original file(use clone attachment macro).
Step 2a; Send the payload to deenveloping to translate the Partner format to Inhouse Flatfile format also do a carbon copy
Step 2b: Use the carbon copied payload and translated to a standard INVOICE Archived Inhouse format
Step 3 : Send the translated file from Step 2a to their backend application.
Step 4: The copied file in Step1 will then need to be merged with translate file from Step 2b
Step 5: File from Step 4 need to be sent to PGP Xproc for (SIGN ONLY).
Step 6 : Send the signed file from Step 5 to backend system called as Spyvision Archive for storage.
On GIODE we can today configure the PGP Xprocessor to only perform ENCRYPT/DECRYPT with or without sign for inbound. But Electrolux request is to not do ENCRYPT/DECRYPT but only SIGN .
The reason being they want to proof that the file is authentic and their backend application Spyvision Archive is able to read the file. Using Action ENCRYPT and sign wont let their Spyvision Archive be able to read the file. There is nothing more they can do about it.
|
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Guest
