You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Andras Salamon (Jira)" <ji...@apache.org> on 2020/07/17 15:11:00 UTC
[jira] [Commented] (SOLR-14663) ConfigSets CREATE does not set
trusted flag
[ https://issues.apache.org/jira/browse/SOLR-14663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159986#comment-17159986 ]
Andras Salamon commented on SOLR-14663:
---------------------------------------
The patch does not contain the documentation changes, first I'd like to get some confirmation that this is a good approach.
> ConfigSets CREATE does not set trusted flag
> -------------------------------------------
>
> Key: SOLR-14663
> URL: https://issues.apache.org/jira/browse/SOLR-14663
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andras Salamon
> Priority: Major
> Attachments: SOLR-14663.patch
>
>
> If I upload a configset using [ConfigSets API|https://lucene.apache.org/solr/guide/8_6/configsets-api.html] UPLOAD Solr sets the trusted flag. The config set will be trusted if authentication is enabled and the upload operation is performed as an authenticated request.
> On the other hand if I use the ConfigSets API CREATE which creates a new configset based on an already uploaded one, this flag will not be set, so the configset will be effectively untrusted.
> I don't really understand the difference here, I think CREATE API call should set this flag just like UPLOAD sets it.
--
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