Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add CAS 1.0 validation failure on invalid service, CAS 2.0 validation failure on invalid service and bad ticket

...

6. reload /validate?service=foo&ticket=[ticket from Step 3]
7. you should get back:

No Format
no\n
\n
CAS 1.0 validation failure (bad ticket, wrong service)

4. visit /validate?service=foo&ticket=foo
5. you should get back:

No Format
no\n
\n

6. visit /validate?service=bar&ticket=[ticket from Step 3]
7. you should get back:

No Format

no\n
\n
CAS 2.0 validation

4. visit /serviceValidate?service=foo&ticket=[ticket from Step 3]
5. you should get back:

...

No Format
<cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>
  <cas:authenticationFailure code='INVALID_TICKET'>
    ticket '\[ticket from Step 3\]' not recognized
  </cas:authenticationFailure>
</cas:serviceResponse>
CAS 2.0 unsuccessful validation (bad ticket, wrong service)

4. visit /serviceValidate?service=foo&ticket=foo
5. you should get back:

No Format

<cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>
  <cas:authenticationFailure code='INVALID_TICKET'>
    ticket 'foo' not recognized
  </cas:authenticationFailure>
</cas:serviceResponse>

6. visit /serviceValidate?service=bar&ticket=[ticket from Step 3]
7. you should get back:

No Format

<cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>
  <cas:authenticationFailure code='INVALID_SERVICE'>
    ticket '\[ticket from Step 3\]' does not match supplied service
  </cas:authenticationFailure>
</cas:serviceResponse>

...