Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>What you propose is possible but I would suggest doing a little reading about how CAS works, the <a href="http://www.jasig.org/cas/protocol" rel="nofollow">CAS Protocol</a> is a good resource.</p> <p>What CAS provides is an authentication provider trusted by each of your websites. It is an additional hosted website / service along side your other websites wanting to use CAS to provide authentication.</p> <p>Based on the information you provided in your example, here is how it would mostly likely play out:</p> <ol> <li><p>User visits the PHP website <code>www.myphpsite.com/login</code>, recognizing the user is not yet authenticated the PHP website redirects the user to your CAS website.</p></li> <li><p>The CAS website also does not recognize the user as authenticated and so presents the user with a login screen. The user enters their credentials which CAS verifies against the database and then redirects the user back to the PHP website.</p></li> <li><p>The PHP website receives a service-ticket from CAS via URL parameter which it verifies with CAS making a back-end web-service call. Having received a confirmation from CAS that the service ticket was valid PHP then logs the user in using its built-in authentication procedure (i.e. instead of validating against the database the PHP website now validates with CAS to assert that a user is authentic).</p></li> <li><p>At this point if the user attempts to access the .NET website <code>www.myDotNetApp.com</code> it would not be able to recognize the user as authenticated using its built-in authentication procedure and so it would redirect the user to the CAS website.</p></li> <li><p>However, the CAS website would already recognize the user as authenticated. Instead of prompting the user to login, CAS would automatically redirect the user back to the .NET website providing a service-ticket as a URL parameter. The .NET website would then make a back-end web-service call to CAS verifying the service-ticket and log the user in using its built-in authentication procedure.</p></li> </ol> <p>In summary, CAS provides a single place for users to authenticate. Other websites can then direct needs for authentication to CAS where CAS either asks the user to login or recognizes the user as already logged and notifies the website. </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