-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fortinet FortiGate WebSession Parsers Parsing Fix & Additions #10865
base: master
Are you sure you want to change the base?
Conversation
@microsoft-github-policy-service agree |
Hi @t-pol, |
Hi @t-pol, |
The issues have been fixed. Thanks |
Thanks @t-pol. |
Hello, is there any feedback regarding the parser ? |
can you please add tester files after testing |
Hi @t-pol, please check above comments from @Alekhya0824 and act accordingly. Thanks |
Hi @t-pol, |
Results of tests have been uploaded. Thanks |
Thanks @t-pol. |
Hello, is there any feedback regarding the parser ? |
hi @t-pol We have made some changes to our github validation script, can you please pull latest changes from upstream repo? |
The changes have been merged. |
Hello @vakohl , Is there any feedback regarding this ? |
Parsers/ASimWebSession/Tests/Fortinet_FortiGate_ASimWebSession_SchemaTest.csv
Show resolved
Hide resolved
Parsers/ASimWebSession/Tests/Fortinet_FortiGate_ASimWebSession_DataTest.csv
Show resolved
Hide resolved
@t-pol Can you please help attaching sample data for the parser? You can anonymize data before uploading |
Validations are failing due to this |
Hi @t-pol, |
Hi @t-pol, |
Required items, please complete
Change(s):
Reason for Change(s):
When there is no User Agent string in AdditionalExtensions, the parsing of HttpRequestMethod fails.
Incorrect parsing of HttpRequestMethod and HttpUserAgent.
Adding NetworkApplicationProtocol field in the project-rename. (Optional field in the parser, but it exists in FortiGate logs)
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present: