TheHokieCoder

Also, should we make CAS v3.0 the default protocol for new installs (via the web.config.install.xdt file)? We obviously don't want to overwrite an existing config to switch to v3.0, but...

@HamidRezaAshkiyan Unfortunately this CAS client currently does not support the CAS version 3 protocol, as is evident by this issue to add support for the protocol to the project. Furthermore,...

@HamidRezaAshkiyan Unfortunately, no, there is no NuGet package for my fork of the project because I don't plan on releasing the client on my own. The plan is to implement...

@phantomtypist I stumbled across this issue just now because I realized that my personal settings for indentation messed up the formatting of code that was merged from my recent pull...

@KirschnerMatt are you still experiencing this issue/have this need? I am trying to help work on the open issues for the project, so if you still want this answered I'll...

@KirschnerMatt Thanks for the quick reply back. Glad to hear you worked out a solution. @serac OK to close this (now) non-issue?

Sounds good. I'll add it to my to-do list. Any feedback/suggestions from other contributors on how this might best be accomplished will be greatly appreciated.

@MostafaMahdy Unfortunately the CAS v1.0 specification does not support user attributes. It only supports providing the asserted identity of the user who logged in. See the specification details for more...

My apologies, @MostafaMahdy. It's been quite a while since I've worked with this project, so I forgot that CAS v3 support is currently only experimental and not yet merged into...

@MostafaMahdy Would you please provide what you have configured for your `casClientConfig` section of your web.config file? Before posting that section here, though, please scrub any sensitive details about your...