search

dlindahl / omniauth-cas

A CAS OmniAuth Strategy
MIT License
88 stars 79 forks source link

Handling CAS 1 Architecture Service Validate Response #17

Closed jithendhir92 closed 10 years ago

jithendhir92 commented 10 years ago

I'm using omniauth-cas 1.0.4 to authorize my users with a cas server. But the server supports CAS 1 architecture but the gem supports CAS 2 architecture .

The CAS 1 service validator responds with two lines (in a text/plain HTTP response); the first line is either yes or no, corresponding to whether the ticket that the application presented is valid or not. If the ticket is valid, the second line contains the NetID of the ticket holder - that is, the identification of the user who has authenticated successfully. If the ticket is invalid, the second line is empty. Thus, an example response is: yes peon If the ticket was valid, the CAS immediately removes it so that it cannot be used again. But CAS 2 architecture responds with a XML snippet. How to support CAS 1 architecture Service Validate Response ?

dlindahl commented 10 years ago

I never intended to support CAS1, but I am not opposed to adding support if there is a demand for it. If you want to mock up an implementation, I will take a look and add it. Or you can submit a full PR.

dlindahl commented 10 years ago

Closing this in favor of a user-submitted Pull Request