Consent TOU key naming/logging

[Charles R. Tompkins]

How does one go about renaming the TOU key in IdPv3 from "example-tou-n" to
something else?

When I edit messages/consent-messages.properties and add a TOU message:
someDescriptive-tos = example-tou-2
..I have to preserve the "example-tou-n" format.  

I could care less what it's called, but for the log line:
"13:55:51.598 - INFO [Shibboleth-Consent-Audit.SSO:241] -
idpSessionId[],JSESSIONID[],clientIP[] -
20151028T175551Z|urn:edu:ufl:idp:qat|TermsAccepted|user|example-tou-2||true"
...where I'd expect to see "someDescriptive-tos" instead of "example-tou-2."

If I try to create a separately named TOU message:
someOtherDescriptive-tos = myDescriptive-tou-1
...the IdP can't find it and supplies default/filler text.

Where do I configure the v3 IdP to look for a TOU that doesn't start with
the name "example" or actually log the key's name?


Thanks,

Charles Tompkins
UF Information Technology
Enterprise Infrastructure and Operations

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4793 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20151028/06efd0d7/attachment.p7s>