Skip to content
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

Geo Location in Alert Evidence breaks Json structure #3056

Open
SimonDubex opened this issue Dec 19, 2024 · 0 comments
Open

Geo Location in Alert Evidence breaks Json structure #3056

SimonDubex opened this issue Dec 19, 2024 · 0 comments
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience

Comments

@SimonDubex
Copy link

SimonDubex commented Dec 19, 2024

Describe the bug

When retrieving alerts from the Security endpoint. The following Security.ipEvidence breaks the Json Structure. As the longtitude contains a comma and is not quoted.
{
"@odata.type": "#microsoft.graph.security.ipEvidence",
"ipAddress": "52.163.67.31",
"countryLetterCode": "SG",
"location": {
"countryName": "Singapore",
"state": "Central Singapore",
"city": "Singapore",
"longitude": 1,038518E+07,
"latitude": 128795
},

Expected behavior

Quote the longitude value or handle longtitude as another data type

How to reproduce

Create a json alert object, including the following information
{
"@odata.type": "#microsoft.graph.security.ipEvidence",
"ipAddress": "52.163.67.31",
"countryLetterCode": "SG",
"location": {
"countryName": "Singapore",
"state": "Central Singapore",
"city": "Singapore",
"longitude": 1,038518E+07,
"latitude": 128795
},

SDK Version

Microsoft.Graph.Security 2

Latest version known to work for scenario above?

2.20.0 and 2.23.0

Known Workarounds

Replacing the Longtitude value manually if it exists

Debug output

Click to expand log ```
</details>


### Configuration

Name                           Value                                                                                    ----                           -----                                                                                    PSVersion                      5.1.17763.6530                                                                           PSEdition                      Desktop                                                                                  PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                  BuildVersion                   10.0.17763.6530                                                                          CLRVersion                     4.0.30319.42000                                                                          WSManStackVersion              3.0                                                                                      PSRemotingProtocolVersion      2.3                                                                                      SerializationVersion           1.1.0.1

### Other information

_No response_
@SimonDubex SimonDubex added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

1 participant