This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Is it possible to use a SAML proxy as an workaround of LSF PAC that does not support of Azure AD?
We expect to integrate Azure AD into Application Center, but LSF PAC does not support of Azure AD. So I would like to ask the experts from IBM if it is possible to use a SAML proxy as an workaround of LSF PAC that does not support of Azure AD?
I am working on LSF PAC SSO with SAML, The identity provider is Azure AD, So I meet the above issue (LSF PAC does not support of Azure AD).
Our idea: Put a proxy in the front of LSF PAC, the proxy can contact to the Azure AD, and get the token. The user wants to get access to the LSF PAC, he basically contacts the proxy, then the proxy in on behalf of the user basically gets to the Azure AD, and grabs the token for the user so this one is getting the token, and then the proxy can forward the user request with the jason web token in the http header to PSF PAC.
What do you think of this workaround? Have you ever had a similar resolution scenario?
Do not place IBM confidential, company confidential, or personal information into any field.