LDAP Integration Would Be Perfect :-)

[orware]

If you can get some simple fallthrough LDAP Config stuff added in (allowing us to configure multiple LDAP servers to try the authentication against...e.g. a student LDAP server first, then a staff LDAP server if the provided username/password don't work with the student LDAP server) along with configuring which LDAP fields can be included in the cas:attributes section of the response this would be an awesome thing to have available (I really dislike the complexity of other CAS solutions I've had to work with so far).

Throwing the server behind an instance of caddy and having it all just work would be wonderful :-).

[matthewvalimaki]

I've abandoned this project and should state that. The code is not good either :) Reason why I abandoned it was that I fed up with the lack of protocol design really and that the existing versions are really bad. I was better off doing my own protocol. CAS as a protocol lacks completely instructions how to handle different cases (consider HTTP protocol and its codes) and it happily mixes text, html and xml.

With minimal work Kong and its plugins you might be able to do what you want.

[orware]

No worries! For me it was actually a nice simple implementation of the protocol that helped contrast with a PHP version I was also looking at that was more complicated to follow. Overall it looks like you were well on your way, it just seemed to be missing a tie back to an actual user store of some kind from what I could tell. Overall the CAS protocol document does leave some questions unanswered but overall it hasn't been too bad (going from zero last Thursday to building my own super simple implementation that's tied back to LDAP so far seems to be working, though I still have a bit more work to do).

I might circle back around and create a Go version myself once I've finished with the PHP version and have a better understanding of things so I'll likely still come back and refer to yours!