Details
-
Task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
Security Level: Public
-
None
Description
SGCollect currently makes calls to 4985 in order to grab config, status etc.
With the new Authenticated admin API its possible that this won't work.
I think it should be possible to work around it when using sgcollect standalone by supplying creds in the URL via a flag, however, this may not work when called from SGW itself.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Priority | Major [ 3 ] | Blocker [ 1 ] |
Issue Type | Task [ 3 ] | Improvement [ 4 ] |
Assignee | The One [ the one ] | Adam Fraser [ adamf ] |

Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Issue Type | Improvement [ 4 ] | Task [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Should review the set of endpoints that sgcollect uses, and ensure they are available to the RBAC role that we'd expect to be running sgcollect.