After deploying this to some client sites, I found that I was still
having problems. So I've made a further tweak to simply remove the index
name from the document itself. If you do this, then Elasticsearch will
use the index from the request path instead.
** Changed in: mahara
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1457709
Title:
Elasticsearch plugin doesn't work with URL-based access control
Status in Mahara:
In Progress
Bug description:
We changed the Elasticsearch plugin to use the _bulk command to load
data into Elasticsearch. But this poses problems for hosting setups
that are using URL-based access control, as described here:
https://www.elastic.co/guide/en/elasticsearch/reference/1.x/url-
access-control.html
This is because the way Elastica handles the _bulk command, it puts
the index name into the request body: localhost/_bulk, instead of
localhost/index/_bulk
Elasticsearch *can* handle the indexname in the URL for _bulk
commands. But we'll need to patch Elastica to handle it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1457709/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
