You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@senssoft.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2018/04/16 18:00:00 UTC

[jira] [Updated] (SENSSOFT-289) Remove Logstash Dependency for Header Requests

     [ https://issues.apache.org/jira/browse/SENSSOFT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Poore updated SENSSOFT-289:
----------------------------------
    Fix Version/s:     (was: UserALE.js 1.1.0)
                   UserALE.js 1.2.0

> Remove Logstash Dependency for Header Requests
> ----------------------------------------------
>
>                 Key: SENSSOFT-289
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-289
>             Project: SensSoft
>          Issue Type: Task
>          Components: UserALE.js
>    Affects Versions: UserALE.js 1.0.0
>         Environment: JavaScript
>            Reporter: Joshua Poore
>            Assignee: Rob Foley
>            Priority: Major
>             Fix For: UserALE.js 1.2.0
>
>   Original Estimate: 2m
>  Remaining Estimate: 2m
>
> We have previously relied on Logstash to handle requests from the page for data from headers. This is a vulnerability for two reasons: it makes certain information passed to UserALE.js via our API unobtainable and it places a strong dependency on Elastic assets and specific system configurations to get basic data.
> Definition of Done: Header Requests are Made By UserALE.js not LogStash. Remove configs from existing logstash-config. Confirm that when logging, UserALE.js logs from browser tabs are correctly providing data pushed through UserALE.js API (useraleVersion, toolName, toolVersion, userId.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)