Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb Application - User Authentication Across Domains
    text
    copied!<p>A client of ours has approached us to develop an application, and as usual the scope grows day by day.</p> <p>Initially it started as a dedicated app confined within their corporate network. User Authentication was established by aquiring the user's Windows login and using a SQLServer Database to host the access rights. All quite straight forward.</p> <p>They now want the following:<br> <strong>- Application to be Web Based<br> - Application to be hosted outside of the corporate network<br> - User authentication to work in the same way (no using passwords, just windows logins)</strong></p> <p>To complicate it further, they want the various functions of the application to to be usable by another application which just fires of HTTP requests.<br> <strong>- User logs in to corporate network<br> - User launches corporate application<br> - User processes customer details<br> - User clicks a button<br> - Corporate Application fires a HTTP request to our hosted web app<br> - HTTP request included necessary authentication and customer details<br> - User authentication is completed 'automatically' (No human involvement)<br> - Customer data is transmitted securely</strong></p> <p>They are very keen for us to do this for them as our initial approach was very much what they wanted. They still want us to do this even though such hosted web apps are not our speciallity. So I now approach the experts;<br> <strong>- Does anyone have any advice on how to approach this?<br> - Does anyone have any warning about the possible pitfalls to avoid?</strong> </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload