{"_id":"57881d72e516ba0e003047a8","version":{"_id":"56be3388be55991700c3ca10","project":"56be3387be55991700c3ca0d","__v":8,"createdAt":"2016-02-12T19:33:28.313Z","releaseDate":"2016-02-12T19:33:28.313Z","categories":["56be3389be55991700c3ca11","57646709b0a8be1900fcd0d8","5764671c89da831700590782","57646d30c176520e00ea8fe5","5764715d4f867c0e002bc8e3","57698fa2e93bfd190028815c","576c2af16c24681700c902da","5787da96b008c91900aae865"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"project":"56be3387be55991700c3ca0d","user":"5633ec9b35355017003ca3f2","category":{"_id":"5787da96b008c91900aae865","__v":0,"project":"56be3387be55991700c3ca0d","version":"56be3388be55991700c3ca10","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-07-14T18:31:50.937Z","from_sync":false,"order":3,"slug":"troubleshooting","title":"Troubleshooting"},"parentDoc":null,"__v":1,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-07-14T23:17:06.902Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"Are you prompted for a username and password, or receive a 401 Not Authorized response when trying to access your index/admin actions? We currently restrict access to Solr admin handlers due to the need to audit them for security and performance implications in our shared environment.\n\nAs of this writing, there are two exceptions to this policy:\n\n- `/admin/ping` which is used frequently by some Solr clients to check index health. We consider this path deprecated and recommend using `/ping` instead.\n- `/admin/luke` can be used to fetch information about fields present in the index, and has been throttled with `numTerms=0` to prevent a performance problem.\n\nAdmin handlers can be very helpful for debugging, and we recommend you run a local instance of Solr to have full access to its tools in your development environment.\n\nIf your application or its Solr client depends on a restricted admin action, [let us know](mailto:support:::at:::websolr.com) and we can work with you to determine an alternative or audit the specific action for access.","excerpt":"Learn about why you're getting a 401 on accessing index/admin actions, and what to do about it.","slug":"access-restricted-to-solr-admin-actions","type":"basic","title":"Access restricted to Solr admin actions"}

Access restricted to Solr admin actions

Learn about why you're getting a 401 on accessing index/admin actions, and what to do about it.

Are you prompted for a username and password, or receive a 401 Not Authorized response when trying to access your index/admin actions? We currently restrict access to Solr admin handlers due to the need to audit them for security and performance implications in our shared environment. As of this writing, there are two exceptions to this policy: - `/admin/ping` which is used frequently by some Solr clients to check index health. We consider this path deprecated and recommend using `/ping` instead. - `/admin/luke` can be used to fetch information about fields present in the index, and has been throttled with `numTerms=0` to prevent a performance problem. Admin handlers can be very helpful for debugging, and we recommend you run a local instance of Solr to have full access to its tools in your development environment. If your application or its Solr client depends on a restricted admin action, [let us know](mailto:support@websolr.com) and we can work with you to determine an alternative or audit the specific action for access.