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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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 notifications 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.
Enable SAML SSO on secure proxy server
We have an existing requirement as follows.
The trading partners are required to login to myFIlegateway through SSP Http adapter. SSP should be configured to support SSO using 3rd party application. Below is the sequence of events, should happen as per our requirements:
1. A trading partner hits the myFilegateway URL from his/her internet browser.
2. The SSP HTTP Adapter receives the HTTP request in DMZ zone.
3. SSP Http Adapter should redirect the incoming request to 3rd party identity provider application using HTTP along with some Meta Information required by 3rd party identity provider application.
4. The 3rd party identity provider application will receive the HTTP request and present a page to trading partner to fill in credentials like username, password, OTP or secret question or RSA token number etc.
5. The 3rd party identity manager application will authenticate the user based on the credentials entered and respond back to SSP. The response format will be SAML Assertion Message.
6. SSP should parse the SAML Assertion Message and pass the message to SEAS in the format in which SEAS understand.
7. SEAS (with custom java user exit to be build) analyzes the SAML Assertion Message and validates the SAML Assertion Message with expiry time (mentioned in SAML Assertion Message).
8. Once SEAS validates the SAML, then it creates a SESSION Token and returns the SSO token to SSP HTTP Adapter.
9. SSP Outbound Node sends request to myFilegateway.
10. myFilegateway validates the SSO token with SEAS
11. Once validation is completed by myFilegateway, the user lands on myfilegateway home page.
12. Till the session is alive SSP should not redirect user to identity provider.
We understand that, currently Secure Proxy works on principle of SESSION_TOKEN. That SSP redirects the incoming request to 3rd Party Application and can consumes the SAML response in form of cookie/ SESSION_TOKEN in http header.
We want to know if there is any way or any user exit options available to support raw HTTP SAML request and response for interaction between SSP and 3rd party Application.
As per our current security policy SSP does not satisfy the requirements and it has not use.
Link to original RFE
Do not place IBM confidential, company confidential, or personal information into any field.