[
https://issues.apache.org/jira/browse/SOLR-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100245#comment-18100245
]
Jan Høydahl commented on SOLR-18323:
------------------------------------
Your first suggestion would be simpler, but not sure it fixes all cases for all
configurations. Looked through your proposed commit as well, conveying the
principalClaim to frontend, which would is more flexible. You'll just have to
choose a path and propose a PR. If you feel the simpler ui-only approach is
good enough for you, I'd go with it.
> When using JWTAuthPlugin, UI is always showing "sub" value in logout button
> ---------------------------------------------------------------------------
>
> Key: SOLR-18323
> URL: https://issues.apache.org/jira/browse/SOLR-18323
> Project: Solr
> Issue Type: Bug
> Components: Admin UI, Authentication
> Affects Versions: 10.0
> Reporter: Philipp Trulson
> Priority: Minor
>
> We just used JWTAuthPlugin for the first time and noticed that in the legacy
> Admin UI it now says "Logout 907c9070-b23f-422e-b730-279aa0cf3426" instead of
> the actual username, even though we set {{"principalClaim" =
> "preferred_username"}} in the config. In the Audit logger logs this works
> fine, I can see my username there, but in the UI it just breaks the design.
> For most OIDC providers {{sub}} is a stable value that never changes, while
> email addresses and usernames can change, so it should never be used in a UI
> IMHO. A better approach would be to check for the {{principalClaim}} value in
> [login.js|https://github.com/apache/solr/blob/releases/solr/10.0.0/solr/webapp/web/js/angular/controllers/login.js#L150]
> and then show the respective value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
