node-cas
node-cas copied to clipboard
kcbanner
Central Authentication Service (CAS) client for Node.js
this was creating problems with self closing tags. For reference see https://github.com/cheeriojs/cheerio/issues/598
I suppose this was a mistake that was not caught during publishing.
`url.parse("http://foo.com:444/bar").hostname` returns `"foo.com:444"`, which causes `validate` to make an invalid call to `https`. This permits using a CAS running on a different port.
ssl_key: fs.readFileSync('/path/to/private_key.pem'), ssl_cert: fs.readFileSync('/path/to/ssl_cert.pem'),
If the ticket isn't a proxy ticket (PT-) then we should use servicevalidate.
Hi, Are you planning also on releasing the latest + bumped version to the npm package repo too?
After upgrading to node 0.10, the https module defaults to checking SSL certs and throwing an error if it encounters a self-signed cert. Our CAS is hosted on a server...
Some CAS server does not have both end point. So we have determine which validate end point they have.
This library converts CAS attribute names to lowercase ([example](https://github.com/kcbanner/node-cas/blob/fcd27dad333223b3b75a048bce27973fb3ca0f62/lib/cas.js#L1026)). This is not prescribed by the CAS protocol specification. Note that the CAS protocol documentation even includes an example of a...
