Legal issueshttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues2024-03-25T12:17:31Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/48Unexpected behavior related to expiration date for GC, Azure, IBM and RI envi...2024-03-25T12:17:31ZDébora BarrettoUnexpected behavior related to expiration date for GC, Azure, IBM and RI environmentsBased on the [documentation](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/docs/tutorial/ComplianceService.md?ref_type=heads#expiration-date), the legal tag must become invalid when it reaches ...Based on the [documentation](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/docs/tutorial/ComplianceService.md?ref_type=heads#expiration-date), the legal tag must become invalid when it reaches the expiration date and the records ingested with them should become inactive. After updating the expiration date, the legal tag must become valid again and the records active.
During the legal service tests performed for M20 Preshipping, the legal tag created for GC, Azure and RI with expiration date set for 29-09-2023 didn't became invalid at this date (see below). Same happened with IBM, with expiration date set for 02-10-2023.
For AWS it was possible to observe the expected behavior as documented [here](https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M20/Test_plan_Results_M20/Core%20services/M20_AWS_Legal_Service_-_Debora.md).
- Azure
```
{
"name": "opendes-Manifest-Ingestion-Legal-Tag-expdate",
"description": "Legal Tag added for Manifest Based Ingestion",
"properties": {
"countryOfOrigin": [
"US",
"CA"
],
"contractId": "123456",
"expirationDate": "2023-09-29",
"originator": "Autotest",
"dataType": "Third Party Data",
"securityClassification": "Private",
"personalData": "No Personal Data",
"exportClassification": "EAR99"
}
```
- GC
```
{
"name": "m19-Manifest-Ingestion-Legal-Tag-expdate",
"description": "Legal Tag added for Manifest Based Ingestion",
"properties": {
"countryOfOrigin": [
"US",
"CA"
],
"contractId": "123456",
"expirationDate": "2023-09-29",
"originator": "Autotest",
"dataType": "Third Party Data",
"securityClassification": "Private",
"personalData": "No Personal Data",
"exportClassification": "EAR99"
}
```
- RI
```
{
"name": "osdu-Manifest-Ingestion-Legal-Tag-expdate",
"description": "Legal Tag added for Manifest Based Ingestion",
"properties": {
"countryOfOrigin": [
"US",
"CA"
],
"contractId": "123456",
"expirationDate": "2023-09-29",
"originator": "Autotest",
"dataType": "Third Party Data",
"securityClassification": "Private",
"personalData": "No Personal Data",
"exportClassification": "EAR99"
}
```
- IBM
```
{
"name": "opendes-Manifest-Ingestion-Legal-Tag-expdate",
"description": "Legal Tag added for Manifest Based Ingestion",
"properties": {
"countryOfOrigin": [
"US",
"CA"
],
"contractId": "123456",
"expirationDate": "2023-10-02",
"originator": "Autotest",
"dataType": "Third Party Data",
"securityClassification": "Private",
"personalData": "No Personal Data",
"exportClassification": "EAR99"
}
}
```https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/42GET and DELETE /api/legal/v1/legaltags/{name}2023-11-27T05:35:44ZShane HutchinsGET and DELETE /api/legal/v1/legaltags/{name}Received a response with 5xx status code: 500
Very odd response: ", status: 500"
Should have been a 404.
Run this get curl command to reproduce this failure:
curl -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: osdu...Received a response with 5xx status code: 500
Very odd response: ", status: 500"
Should have been a 404.
Run this get curl command to reproduce this failure:
curl -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: osdu' https://osdu.r3m18.preshiptesting.osdu.aws/api/legal/v1/legaltags/%0A
Run this cURL command to reproduce this failure:
curl -X DELETE -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: osdu' https://osdu.r3m18.preshiptesting.osdu.aws/api/legal/v1/legaltags/%0D
Found this on AWS and Azure.
Run this cURL command to reproduce this failure:
curl -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: opendes' https://osdu-ship.msft-osdu-test.org/api/legal/v1/legaltags/%0A
curl -X DELETE -H 'Authorization: Bearer TOKEN' -H 'Cookie: JSESSIONID=IDHERE'-H 'data-partition-id: opendes' https://osdu-ship.msft-osdu-test.org/api/legal/v1/legaltags/%0Dhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/41GET /api/legal/v1/jobs/updateLegalTagStatus timeout2023-09-26T14:57:13ZShane HutchinsGET /api/legal/v1/jobs/updateLegalTagStatus timeoutI'm getting a timeout from https://osdu.r3m18.preshiptesting.osdu.aws/api/legal/v1/jobs/updateLegalTagStatus
Run this curl command to reproduce this failure:
curl --connect-timeout 60 --max-time 60 -X GET -H 'Authorization: Bearer ...I'm getting a timeout from https://osdu.r3m18.preshiptesting.osdu.aws/api/legal/v1/jobs/updateLegalTagStatus
Run this curl command to reproduce this failure:
curl --connect-timeout 60 --max-time 60 -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: osdu' https://osdu.r3m18.preshiptesting.osdu.aws/api/legal/v1/jobs/updateLegalTagStatus
GET /api/legal/v1/jobs/updateLegalTagStatus on Azure
curl -X GET -H 'Authorization: Bearer TOKEN' -H 'data-partition-id: opendes' https://osdu-ship.msft-osdu-test.org/api/legal/v1/jobs/updateLegalTagStatushttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/28[BUG] Swagger page could not be displayed2023-08-07T09:36:54ZRostislav Vatolinvatolinrp@gmail.com[BUG] Swagger page could not be displayedSwagger page could not be displayed after recent upgrade of springfox-boot-starter to 3.0.0Swagger page could not be displayed after recent upgrade of springfox-boot-starter to 3.0.0https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/27Optimal memory and cpu configuration to stand against load2023-08-07T09:37:15ZRostislav Vatolinvatolinrp@gmail.comOptimal memory and cpu configuration to stand against loadPlease conduct load tests to see the optimal configuration for legal service in Azure environment.
Please update hpa and resources configuration.Please conduct load tests to see the optimal configuration for legal service in Azure environment.
Please update hpa and resources configuration.Rostislav Vatolinvatolinrp@gmail.comRostislav Vatolinvatolinrp@gmail.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/11Upgrade Core Azure Dependency2022-02-11T22:02:36ZDavid Diederichd.diederich@opengroup.orgUpgrade Core Azure Dependency