https://lukemurphey.net/https://lukemurphey.net/favicon.ico2018-05-16T20:44:59ZLukeMurphey.netLookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62512018-05-16T20:44:59ZLuke Murphey
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/2194">Bug #2194</a>: Incorrect "The lookup file could not be saved" appears for non-admin users</i> added</li></ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62532018-05-16T20:45:02ZLuke Murphey
<ul><li><strong>Target version</strong> set to <i>3.2.0</i></li></ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62542018-05-16T21:42:12ZLuke Murphey
<ul></ul>Questions:
<ul>
<li>What version of Splunk and browser was this observed on?
<ul>
<li>6.6.3, FireFox 54</li>
</ul>
</li>
<li>What is the trace?</li>
<li>Is this server-side failure?
<ul>
<li>Yes, it is getting a 500 code</li>
<li>No message is included, just "Unable to save the lookup" </li>
</ul>
</li>
<li>Does this repro locally?
<ul>
<li>No</li>
</ul>
</li>
<li>Where specifically is the call failing?</li>
</ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62552018-05-17T17:05:43ZLuke Murphey
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62562018-05-17T18:45:47ZLuke Murphey
<ul><li><strong>Subject</strong> changed from <i>Lookup file could not be saved message</i> to <i>Lookup file could not be saved due to lookup replication call returning 403</i></li></ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62572018-05-17T18:47:38ZLuke Murphey
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul> Lookup Editor - Bug #2257: Lookup file could not be saved due to lookup replication call returning 403https://lukemurphey.net/issues/2257?journal_id=62582018-05-17T18:48:30ZLuke Murphey
<ul><li><strong>Target version</strong> changed from <i>3.2.0</i> to <i>3.0.2</i></li></ul>