CAS Encoded Ticket & CAS User

[Marvin Addison]

On Fri, Jan 18, 2019 at 11:35 AM Ryan Rumbaugh <rrumbaugh at nebraska.edu> wrote:
> <bean parent="CAS.ValidateConfiguration" p:userAttribute="uid" />
> When making the above change I have verified the <cas:user> is indeed the correct attribute (uid).

That's all that matters in terms of communicating the attribute to use
as the CAS username in the CAS v2 ticket validation response.

> However, the CAS service I’m testing with displays a message that my ID is not found

Service is an overloaded term, so let me disambiguate. I understand
service to mean "CAS-enabled application." In that case all that
matters is what is in the cas:user element of the protocol message
sent to the application. It sounds as if you have verified the correct
value in the protocol message, which is all that matters.
Canonicalization is a distant memory at that point.

M