Project

General

Profile

Bug #2257

Lookup file could not be saved due to lookup replication call returning 403

Added by Luke Murphey over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Luke Murphey
Target version:
3.0.2
Start date:
05/16/2018
Due date:
% Done:

100%

Related issues

Related to Lookup Editor - Bug #2194: Incorrect "The lookup file could not be saved" appears for non-admin users Closed 01/31/2018

Associated revisions

Revision 519 (diff)
Added by lukemurphey over 6 years ago

Handling 403 response to the replication call

Also, updating to version 2.7.2.

Reference #2257

Revision 520 (diff)
Added by lukemurphey over 6 years ago

Fixing quote mark

Reference #2257

Revision 521 (diff)
Added by lukemurphey over 6 years ago

Better handling 403 response to lookup replication call

Reference #2257

History

#1 Updated by Luke Murphey over 6 years ago

  • Related to Bug #2194: Incorrect "The lookup file could not be saved" appears for non-admin users added

#2 Updated by Luke Murphey over 6 years ago

  • Target version set to 3.2.0

#3 Updated by Luke Murphey over 6 years ago

Questions:
  • What version of Splunk and browser was this observed on?
    • 6.6.3, FireFox 54
  • What is the trace?
  • Is this server-side failure?
    • Yes, it is getting a 500 code
    • No message is included, just "Unable to save the lookup"
  • Does this repro locally?
    • No
  • Where specifically is the call failing?

#4 Updated by Luke Murphey over 6 years ago

  • % Done changed from 0 to 50

#5 Updated by Luke Murphey over 6 years ago

  • Subject changed from Lookup file could not be saved message to Lookup file could not be saved due to lookup replication call returning 403

#6 Updated by Luke Murphey over 6 years ago

  • Status changed from New to Closed
  • % Done changed from 50 to 100

#7 Updated by Luke Murphey over 6 years ago

  • Target version changed from 3.2.0 to 3.0.2

Also available in: Atom PDF