https://community.splunk.com/t5/Getting-Data-In/License-slave-to-master-REST-API-calls/m-p/372070#M67529 <P>We do not recommend restricting access like this. Your license slaves should have full tcp access to the admin port on your license master (default is tcp/8089.) </P> Tue, 27 Jun 2017 13:10:21 GMT esix_splunk 2017-06-27T13:10:21Z https://community.splunk.com/t5/Getting-Data-In/License-slave-to-master-REST-API-calls/m-p/372069#M67528 <P>Hello guys,</P> <P>is it possible to know which REST calls (if it's the case) are done when license slave is reporting its usage to master?</P> <P>We want to restrict URLs in order to allow only license connections.</P> <P>Thanks for your help.</P> Tue, 27 Jun 2017 12:50:12 GMT https://community.splunk.com/t5/Getting-Data-In/License-slave-to-master-REST-API-calls/m-p/372069#M67528 splunkreal 2017-06-27T12:50:12Z https://community.splunk.com/t5/Getting-Data-In/License-slave-to-master-REST-API-calls/m-p/372070#M67529 <P>We do not recommend restricting access like this. Your license slaves should have full tcp access to the admin port on your license master (default is tcp/8089.) </P> Tue, 27 Jun 2017 13:10:21 GMT https://community.splunk.com/t5/Getting-Data-In/License-slave-to-master-REST-API-calls/m-p/372070#M67529 esix_splunk 2017-06-27T13:10:21Z