Skip to Main Content
Cloud Platform

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

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 a notification 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Submitted
Categories ClearCase
Created by Guest
Created on Jun 27, 2022

ClearCase compatibility with Azure AD

a. How from Architectural perspective Azure AD joined devices are not supported (since it is the future)? From a technical point of view, it is actually not currently possible to do this on Windows hosts because Azure AD is not backward compatible with "legacy" AD. The process token that ClearCase needs does not contain the Azure AD groups in ANY fashion. Thus an "on prem" (or laptop) host that is ONLY a member of an Azure AD domain will not have any group membership. A "legacy" AD Domain is REQUIRED for the ClearCase Windows LAN client to function. In theory, since Azure AD apparently has an LDAP interface, a Linux server may work against Azure AD but that has not been tested. (AD team) : It’s not true in Azure AD we have 2 options are available now as below to have group info in SAML response. Group based possible to configured with that required group information travel. We can create group respective roles in Azure AD and map with group. By that way also group information possible to travel in SAML response. Apart from LDAP Azure AD also start supporting Kerberos after doing some tweaks for your reference below URL may helps you to understand and figure out solution for clearcase. https://techcommunity.microsoft.com/t5/itops-talk-blog/deep-dive-how-azure-ad-kerberos-works/ba-p/3070889 b. The upcoming roadmap of the product to make it support for future ? I have to check this further internally before I can give a definite answer, will get back to you on this. (AD Team) : Please try it with much faster way because even MS itself started session to remove onprem AD and move workload to Azure AD. So, try to make changes or supportable option in CC for Azure AD auto pilot devices.
Idea priority High