You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2021/02/25 15:59:00 UTC
[jira] [Commented] (SOLR-15194) JWTIssuerConfig only allows HTTPS
urls, not HTTP, which is overly strict.
[ https://issues.apache.org/jira/browse/SOLR-15194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291010#comment-17291010 ]
Houston Putman commented on SOLR-15194:
---------------------------------------
I think this is a good idea.
People also may be terminating TLS before a request hits Solr. So while Solr does not have TLS enabled, that does not mean requests are not protected.
> JWTIssuerConfig only allows HTTPS urls, not HTTP, which is overly strict.
> -------------------------------------------------------------------------
>
> Key: SOLR-15194
> URL: https://issues.apache.org/jira/browse/SOLR-15194
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: security
> Affects Versions: master (9.0), 8.8.1
> Reporter: David Eric Pugh
> Assignee: David Eric Pugh
> Priority: Minor
>
> Setting up JWT should always be done with HTTPS urls, but especially in dev and test, require HTTPS is too much.
> Let Solr relax a bit, and log a warning if the url is HTTP versus HTTPS.
>
> Keycloak, out of the box for example doesn't have SSL enabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org