XmlCallObject and Single-Sign-On

o_dejan

Member
We have an ASP.NET application that uses the XmlCallObject to communicate with the JDE Enterprise Server and invoke business functions and this works great as long as native JDE authentication is used. However, a client of ours has configured Single-Sign-On for their JDE environments (Oracle AS, Oracle Internet Directory) and they would like to use the same authentication process with our application. We can relatively easily implement support for SSO process and protect the link of our application so all requests are routed through the SSO server, but...

Since we need the username and password to initialize a XmlCallObject session and we do not have the password of the user, the question is raised how to continue to use XmlCallObject with the identity of a user who is actually logged in through the SSO server and not to be forced to use a proxy user with a known password?

I am hoping I clearly explained what the problem is...

Thanks
 
Back
Top