Skip to Main Content
Integration


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).


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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Status Functionality already exists
Workspace DataPower Gateway
Created by Guest
Created on Apr 24, 2023

Enable API Connect v10 to support AES encryption with Kerberos secured IIS web applications running on Windows Server 2019

Currently, we use RC4_HMAC_MD5 encryption to allow API Connect to securely authenticate to Kerberos-secured web applications running on Server 2008 - Server 2016.  However, with Server 2019, the server hardening security recommendations have changed, and older, less secure encryption ciphers (like RC4_HMAC_MD5) are no longer enabled. 

According to the API Connect development team, API Connect does not support AES encryption for Kerberos security.

We need API Connect to support AES encryption types so that we can securely authenticate to Kerberos-secured web apps running on Server 2019+.

Idea priority Urgent
  • Guest
    Reply
    |
    Jul 12, 2024

    Thanks Ulas.
    For anyone who may still be following this one.:

    Back in Q3 of 2023, IBM released a technote "DataPower Integration with Microsoft Kerberos Protocol Extensions: Service For User (S4U) and Constrained Delegation" with APIC changes/AD domain config to utilize the S4U process for generating kerberos tickets that are AES encrypted.

    We followed the technote and were able to successfully use the "XSLT Kerberos APREQ to S4U2Proxy" option to have APIC DP gateways call a kerberos-secured IIS web app running on Server 2019 with domain controllers patched to disable RC4_HMAC_MD5.

  • Admin
    Ulas Cubuk
    Reply
    |
    Jul 12, 2024

    Hi - We already support AES. I notice that you originally had several support cases opened against this, and it's possible that you may have run into a variant of the issue introduced by the Microsoft KDC patch. 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.

    I would suggest re-trying after addressing the Microsoft KDC patch and validate if there are any algorithm-dependency aspect to the issue.