[JIRA] (JOIDCRP-18) Change RP OIDC.SSO profile bean names

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDCRP-18 ( https://shibboleth.atlassian.net/browse/JOIDCRP-18?atlOrigin=eyJpIjoiMWE1NzcxNTI0MGZiNGVlYWJmZmIzMmM2ZTQ5MDk5NzIiLCJwIjoiaiJ9 )

Re: Change RP OIDC.SSO profile bean names ( https://shibboleth.atlassian.net/browse/JOIDCRP-18?atlOrigin=eyJpIjoiMWE1NzcxNTI0MGZiNGVlYWJmZmIzMmM2ZTQ5MDk5NzIiLCJwIjoiaiJ9 )

I wasn’t thinking about the plugin implications. That’s solveable though, we could move the bean definition into a postconfig installed by the commons plugin.

Now, is that a good idea? I’m less sure. I think it’s probably ok, simply because that definition is ultimately bound to the definition of the class, which is in commons anyway. So I don’t know that I see any real argument there that it would ever conflict, it’s pretty much lockstep. Arguably in fact it’s a step we need to take, because right now the OP supplies the bean but the commons plugin the class. That’s probably not good.

So I’ll lean towards saying we put it in commons.

( https://shibboleth.atlassian.net/browse/JOIDCRP-18#add-comment?atlOrigin=eyJpIjoiMWE1NzcxNTI0MGZiNGVlYWJmZmIzMmM2ZTQ5MDk5NzIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDCRP-18#add-comment?atlOrigin=eyJpIjoiMWE1NzcxNTI0MGZiNGVlYWJmZmIzMmM2ZTQ5MDk5NzIiLCJwIjoiaiJ9 )

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#100206- sha1:1c596f6 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/6b6d5503/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-9c7e910c-8c53-4b17-a34e-d9f6f5cf0207
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/6b6d5503/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-0055b34d-1b4f-4c2f-b33c-50045d652dbb
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/6b6d5503/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-8eab572d-a7b2-41da-a192-28347b672055
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/6b6d5503/attachment-0005.png>