Then, researching the xml parsing and responses.rb, I arrived to this in line 55:
cas_user = @xml.elements["cas:user"]
cas_user is always nil because there is no cas:user element in the XML root, but there's one as child of cas:attributes, thus this:
@xml.elements["cas:attributes/cas:user"]
returns something, in my case, something that looks like a digest of some kind, though I don't know how it's encoded or what info is there.
My question is, if that cas:attributes/cas:user attribute is the one that the client is trying to parse from the XML, or if it's something else. Also, I'd like to know if that XML format I pasted above is CAS-2.0 protocol compliant or if the error comes from a badly-formed XML. It's strange that rubycas-client stores all the "useful data" inside the extra_attributes.
When using CAS-client following the instructions, I've reached a point where I've got a positive response from an external CAS server:
And the XML is like this:
Then I get this log message from rubycas-client:
And then this error dump:
Examining the code, I've come to the conclusion that the error is in filter.rb line 64:
Debugging, I examined the contents of the st object:
Then, researching the xml parsing and responses.rb, I arrived to this in line 55:
cas_user is always nil because there is no cas:user element in the XML root, but there's one as child of cas:attributes, thus this:
returns something, in my case, something that looks like a digest of some kind, though I don't know how it's encoded or what info is there.
My question is, if that cas:attributes/cas:user attribute is the one that the client is trying to parse from the XML, or if it's something else. Also, I'd like to know if that XML format I pasted above is CAS-2.0 protocol compliant or if the error comes from a badly-formed XML. It's strange that rubycas-client stores all the "useful data" inside the extra_attributes.
I'm using the following:
Thanks your your help.