[09:02:39 CDT(-0500)] <fairwinds> serac: gmorning. Am writing a CAS client for my node.js projects. What is the norm, CAS1 or CAS2
[09:06:08 CDT(-0500)] <fairwinds> serac, apetro: Also, looking at what determines what comes back from CAS. I am only looking for id of user back in response for my apps
[09:13:33 CDT(-0500)] <serac> CAS2 (XML) is the standard these days.
[09:15:19 CDT(-0500)] <fairwinds> serac: k, I will have to throw in an xml parser 
[09:15:41 CDT(-0500)] <serac> It's so simple and invariant you could use string manipulation if needed.
[09:16:22 CDT(-0500)] <fairwinds> There seem to be a couple of folks that have given a client a go with nodejs
[09:16:27 CDT(-0500)] <serac> Actually a good Pattern would be a one-liner to get the username.
[09:28:02 CDT(-0500)] <fairwinds> serac: is there a CAS coming with a JSON response?
[09:38:38 CDT(-0500)] <fairwinds> serac: anyway, hoping to have my js client working today, then on to an erlang client
[09:39:48 CDT(-0500)] <serac> XML is the lingua franca of Web security protocols these days, so it's doubtful we'll ever support JSON.
[09:40:09 CDT(-0500)] <serac> Feel free to open a Jira issue for it if you can make a good case.
[09:40:38 CDT(-0500)] <serac> Better, do some research and then discuss on cas-dev – then open Jira issue.
[09:40:48 CDT(-0500)] <serac> Some community discussion around it might be interesting.
[09:41:51 CDT(-0500)] <fairwinds> serac: k, sure. Here's something I found http://code.google.com/p/erlangcas/source/browse#svn%2Ftrunk
[09:42:06 CDT(-0500)] <fairwinds> serac: a cas server in erlang, go figure
Manage space
Manage content
Integrations