This is an IBM Automation portal for Cloud Platform 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
UCD - OpenIDC needs to support integration with AD authorization for Enterprise DevOps
We are in the process of proving out OpenIDC as our SSO solution for UCD 18.104.22.168 and finding the solution incomplete.
We expect Authentication through OpenID to work like Active Directory (AD), without the user having to supply a password
This does not appear to be true in the current instantiation.
In the current implementation, there does not appear to be a hook to bind authorization to authentication.
When a user logs in using OpenIDC, they have no privileges. This is not a useable solution for an enterprise implementation.
As a SOX-critical enterprise DevOps tool, managing authorization is critical.
The current AD method works well:
1. appTeam managers manages AD groups. Adding/deleting members from groups is a standard part of managing a team.
Team membership is regularly audited. There are over 1,500 groups participating in UCD.
2. Groups are added to UCD roles in UCD Teams -- this is a one-time onboarding setup
3. UCD maintains the current user authorized groups by querying AD at login time and populating group membership.
Authorization method is part of the authentication configuration.
This is a critical feature for our Risk Team -- they want proof that we don't allow improper access to users that have left a role
The ask is to include an authorization configuration as part of the authentication configuration
Do not place IBM confidential, company confidential, or personal information into any field.