[
https://issues.apache.org/jira/browse/SOLR-16897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746566#comment-17746566
]
Eric Pugh commented on SOLR-16897:
----------------------------------
The only CLI that I've used regularly that does this is Heroku's client...
You run the CLI, it prompts you to open a browser, you authenticate, and then
the browser says you can close the window, and then the CLI continues on.
I've looked around for some Java open source code that demonstrates this flow,
but haven't had any luck.
My mental model is that the bin/solr would attempt to contact Solr API, see the
login is needed, and then prompt the user to open the Solr Admin and
authenticate. Then the CLI would contact Solr and somehow get back the right
tokens, and let you continue to use them. My simpler approach would be to
have you log into Solr, and in the Admin UI give you the appropriate token to
use on the command line.....
Do you know of any examples that I could look at?
> add support of OAuth 2.0/OIDC 'code with PKCE' flow (back-end)
> --------------------------------------------------------------
>
> Key: SOLR-16897
> URL: https://issues.apache.org/jira/browse/SOLR-16897
> Project: Solr
> Issue Type: Improvement
> Reporter: Lamine
> Priority: Minor
>
> This is the "back-end" part of '[code with
> PKCE|https://issues.apache.org/jira/browse/SOLR-16896]' contribution.
> The back-end code is mainly for configuration. This is where the different
> options are configured.
> This PR adds _tokenEndpoint_ and _authorizationFlow_ options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
