great news Misagh!
Am 04.12.2013 um 16:22 schrieb Misagh Moayyed <[email protected]>: > Here are the test results: > > Java CAS client passes all tests, and is able to support flattened attributes > as they are now in the validation response. I then implemented support for > attributes to be individually listed [1] and tested again. All passed. > > .NET CAS client does not yet support attributes in the validation response, > but it's able to gracefully ignore the extra pieces and move forward. I'd > imagine that we at some point would implement a Cas30 validator to inject > attributes into the assertion. > > Coincidentally, while testing the .NET client I also found an issue with > proxy authentication failure and how the error message in the response was > incorrectly encoded. Here's a pull that addresses that issue [2] > > Misagh > > [1] https://github.com/Jasig/cas/pull/370 > [2] https://github.com/Jasig/cas/pull/368 > From: "Misagh Moayyed" <[email protected]> > To: [email protected] > Sent: Tuesday, December 3, 2013 8:06:47 AM > Subject: Re: [cas-dev] CAS Protocol v3 Status > > Right, thanks for clarification. I have set aside some time to review #1381 > and at least test CASC and NETC. Will provide results and pulls as I march > forward with tests hopefully by week's end. > > Misagh > > From: "Marvin Addison" <[email protected]> > To: [email protected] > Sent: Tuesday, December 3, 2013 7:55:25 AM > Subject: Re: [cas-dev] CAS Protocol v3 Status > > > CAS-1283 is supposed to ensure that multi-valued attributes are properly > > encoded in the response unflattened, and then there is CAS-1381 under which > > I am assuming that we want to carry out creation of new endpoints, etc that > > are discussed on this thread. > > CAS-1283 as written implies CAS protocol v3, so the creation of new > endpoints as a solution to provide strict compliance with v3 protocol > seems consistent with the scope of that issue. I'm not sure what, if > anything, we should do about customizations folks have made to shim > attributes into v2 protocol. I would argue that it has been and > continues to be a customization folks will need to support on their > own. > > I think CAS-1381 is a high-level issue that we're using to track > results of integration testing generally, which includes attribute > support in particular. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
