[JIRA] (JOIDC-112) OP_OIDC_MESSAGES log appender to trace all the exchanged protocol messages

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-112 ( https://shibboleth.atlassian.net/browse/JOIDC-112?atlOrigin=eyJpIjoiZTFjMDNjNTQ3MjA4NDRlN2FkMGYyYTJiMjY1M2Y5ZGUiLCJwIjoiaiJ9 )

Re: OP_OIDC_MESSAGES log appender to trace all the exchanged protocol messages ( https://shibboleth.atlassian.net/browse/JOIDC-112?atlOrigin=eyJpIjoiZTFjMDNjNTQ3MjA4NDRlN2FkMGYyYTJiMjY1M2Y5ZGUiLCJwIjoiaiJ9 )

> 
> 
> 
> Did you investigate using a specialized Log wrapper class in order to
> centralize and simplify the Nimbusds formatting?
> 
> 

I don't think I understand what you mean by this, can you please elaborate? We’re not really exploiting any formatting of Nimbusds currently: the current message encoders and decoders simply log the HTTP headers and parameters as they are, without doing any kind message specific handling of the data.

Instead of simply using exactly the same contents for the *PROTOCOL_MESSAGE* appender, I thought about implementing Nimbus object specific helper-methods that would be used for constructing the object-specific log line for the new appender. The HTTP headers and parameters have been used for constructing these Nimbus objects, but the helper-methods would only log this data in a way that’s compatible for production instances.

( https://shibboleth.atlassian.net/browse/JOIDC-112#add-comment?atlOrigin=eyJpIjoiZTFjMDNjNTQ3MjA4NDRlN2FkMGYyYTJiMjY1M2Y5ZGUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-112#add-comment?atlOrigin=eyJpIjoiZTFjMDNjNTQ3MjA4NDRlN2FkMGYyYTJiMjY1M2Y5ZGUiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100201- sha1:5c1db44 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220622/9e0d7de0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-b926e151-6224-4c6b-b62f-7c1a79e432b2
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220622/9e0d7de0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-5822dc0a-7168-4eeb-a380-419513a8ff48
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220622/9e0d7de0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-685773ce-ac16-4fd8-8374-e389d4a5f590
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220622/9e0d7de0/attachment-0005.png>