• Welcome to the upgraded JDELIST forum and thank you for your patience.
    Please restrict discussions and issues regarding the new forum software to the Off Topic forum. We will be monitoring that forum for issues.
    If you have trouble logging in, please reset your password using the forgotten password form: https://www.jdelist.com/community/index.php?lost-password/
    If you are unable to successfully reset your password, please contact us: Click here!
    We hope that you enjoy the upgraded forum.
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

XmlCallObject and Single-Sign-On


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