Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S seismic-dms-service
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 55
    • Issues 55
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Seismic
  • Seismic DMS Suite
  • seismic-dms-service
  • Issues
  • #34
Closed
Open
Issue created Aug 27, 2021 by Kamlesh Todai@todaiksDeveloper

While testing the Seismic API - list of endpoint returning incorrect response.

Not able to retrieve tenant metadata - Get 403 Forbidden response Upon trying to list subproject in a tenant with an exported authorization token - Get 500 Internal Server Error After patching the dataset not able to retrieve the dataset info. Upon trying to patch dataset with invalid/expired authorization token - Get response of 404 Not Found instead of 401 or 403 Upon trying to Validate the ctag of a dataset with an invalid/expired auth token - it successfully validates instead of returning 401 or 403 Upsert tags to a dataset with invalid gtag gives the response of 200 OK instead of 400 or 404 Delete a data set with an invalid datasetid gives the response of 200 OK instead of 400 or 404 Delete a data set with an invalid path gives the response of 200 OK instead of 400 or 404 Retrieve a list of datasets and sub-directories inside a seismic store path with invalid cursor gives Response of 200 OK instead of 400

Attached is the document giving the details of the request and the invalid responses received. SeismicDMS_CollectionNotes.json The collection can be found here https://community.opengroup.org/osdu/platform/testing/-/blob/master/Postman%20Collection/27_CICD_Setup_SeismicDMSAPI/SeismicDMS%20API%20CI-CD%20v2.0.postman_collection.json

The testing was primarily done on IBM and some on AWS. @ChrisZhang @sacha @anujgupta @Wibben

Assignee
Assign to
Time tracking