Virginia Tech has a .NET client, and there's also some Windows stuff
in the unsupported client list.

Virginia Tech collaborated with Princeton to develop the one and only .NET CAS Client [1]. It's the one you should use.

https://wiki.jasig.org/display/CASC/.Net+Cas+Client

I think the integration docs are pretty decent, but we're always taking contributions.

Any suggestions on the best client to use for .NET with SAML for
attribute release?

The .NET CAS Client works great and we use it exclusively with the SAML protocol here. The only problem we've had is with clock skew on Windows hosts since the .NET client is especially strict on enforcing SAML validity windows and for whatever reason our Windows hosts have a problem getting out of time sync with our stratum 2 time servers. Note the ticketTimeTolerance parameter as a workaround, but it's better to get your clocks in sync.

I'm happy to help troubleshoot integration problems with you. Post some logs and we'll go from there.

Marvin Addison
Middleware Services
Virginia Tech

[1] Most if not all of the patches (mostly for SAML support) in https://svn.middleware.vt.edu/svn/middleware/cas/cas-clients/dotnet-cas-client/ got contributed to the official .NET CAS Client. I haven't looked at that source in ages and it's best to assume it's broken.

--
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to