Consent TOU key naming/logging

[Charles R. Tompkins]

On 10/28/2015 04:21 PM, Tom Zeller wrote:
>
>> On Oct 28, 2015, at 3:04 PM, Charles R. Tompkins <crt at ufl.edu> wrote:
>>
>> 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?
>
> The following in messages/consent-messages.properties worked for me :
>
>   # https\://sp.example.org = example-tou-1
>   https\://sp.example.org = my-tou
>   my-tou.title = My Title
>   my-tou.text = My Test
>
> The ‘key’ is the SP entity ID. Hope that helps.
>


Thanks for the clarification, Tom.

-Charles

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3691 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20151028/ddef01e3/attachment.p7s>