[JIRA] (JOIDC-131) Logging of missing relying party ID is confusing

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *created* an issue

IdP Plugin - OIDC OP ( https://shibboleth.atlassian.net/browse/JOIDC?atlOrigin=eyJpIjoiNzEzYzZmZmE3Zjg0NGIzMWI3NGI1ZjI5ZGNlYTNhMmQiLCJwIjoiaiJ9 ) / Bug ( https://shibboleth.atlassian.net/browse/JOIDC-131?atlOrigin=eyJpIjoiNzEzYzZmZmE3Zjg0NGIzMWI3NGI1ZjI5ZGNlYTNhMmQiLCJwIjoiaiJ9 ) JOIDC-131 ( https://shibboleth.atlassian.net/browse/JOIDC-131?atlOrigin=eyJpIjoiNzEzYzZmZmE3Zjg0NGIzMWI3NGI1ZjI5ZGNlYTNhMmQiLCJwIjoiaiJ9 ) Logging of missing relying party ID is confusing ( https://shibboleth.atlassian.net/browse/JOIDC-131?atlOrigin=eyJpIjoiNzEzYzZmZmE3Zjg0NGIzMWI3NGI1ZjI5ZGNlYTNhMmQiLCJwIjoiaiJ9 )

Issue Type: Bug Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1 Assignee: Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) Components: Authorization Endpoint, Token Endpoint Created: 24/Oct/22 5:06 PM Fix Versions: 3.3.0 Priority: Trivial Reporter: Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 )

The InitializeAudienceRelyingPartyContext bean in the token and authz flows does a second initialization of a RP context tree to carry resource/audience information, but if it fails to get hold of an ID to build one for, it logs that as a failure to locate a client_id, which is misleading in this context.

We’ll have to plugin a logging label for that since the code doesn’t know what ID it’s building around.

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

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#100209- sha1:392b984 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221024/cddef5fa/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-d1e17313-dd86-47e6-816f-ac3f8e0380d8
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221024/cddef5fa/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-trivial-4c21b00f-a3c9-4791-9dd0-394a3b0f3653
Type: image/png
Size: 563 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221024/cddef5fa/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-ed2ce9f4-c87a-4791-95d2-ed6dbb799d37
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221024/cddef5fa/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-6452e658-ea60-4ee7-be66-ab918753dbf4
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221024/cddef5fa/attachment-0007.png>