Testing Experimental CAS v3 Support

@HamidRezaAshkiyan, I have created this separate issue for you so that we can discuss attempting to use my CAS v3 protocol support without creating too much off-topic chatter in issue 17.

Please note, again, that the code I have written so far is untested and not guaranteed to work, especially not in a production environment. However, if you want to test it yourself and provide me with feedback:

1. Uninstall the DotNetCasClient NuGet package from your project. This should still leave behind your CAS client configuration in your web.config file.
2. Clone the dev-issue-17 branch of my repository to your development machine.
3. In your project (in Visual Studio), add a reference to the project you just cloned. This will cause Visual Studio to build the clone of DotNetCasClient when building your project, since it is now a dependency.
4. In your web.config file, locate the casClientConfig configuration section and modify the ticketValidatorName attribute to be Cas30 instead of Cas20.
5. If you are able to successfully build your project, you should now be able to run it.

Let me know if you run into any issues with the above steps. And definitely let me know what did and didn’t work if you were able to successfully compile and run my version of the CAS client.

[TheHokieCoder]

@HamidRezaAshkiyan Sounds good. I was just checking in as sometimes the original poster forgets to check back and let us know how things are going. Let us know when you are able to get your CAS server issue resolved and are then able to test out the CASv3 support. Thanks!

[HamidRezaAshkiyan]

Unfortunately, Server admin doesn’t respond and I couldn’t solve problem on my own so close this issue or if you like keep it open for other to contribute and if anything changed i will come back and say it here. Thanks.