This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
If You need to start secured communication from DP GW (or ACE) to modern Windows Servers normally You could use Kerberos client keytabs. After recent changes in Kerberos / Netbios protocols Microsoft "say goodby" to last availble encription method RC4 HMAC NT (DES never was available in any modern Windows Servers like Windows Server 2012 and newer). So currently there is no way to use secured communication (basic authentication not count as "secure") using "service" accounts in cases were DP GW initiate communication.
Idea priority | Urgent |
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.
Hi - We already support algorithms other than RC4, like AES. It's possible that you may have run into a variant of the issue introduced by the Microsoft KDC patch. Also separate from what algorithms we support is what key(s) are put into the keytab and whether the keytab was correctly created for each change in KDC configuration. Please see the similar conversation here https://integration-development.ideas.ibm.com/ideas/APICONN-I-705
I would suggest re-trying after addressing the Microsoft KDC patch and validate if there are any algorithm-dependency aspect to the issue.