Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • 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 16
    • Merge requests 16
  • 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
  • #33
Closed
Open
Issue created Aug 04, 2021 by Kamlesh Todai@todaiksDeveloper

Inconsistent behavior across CSPs - while Registering/creating seismic-dms tenant

POST .../tenant​/{tenantid} Register a seismic-dms tenant. The API document says Required roles: seistore.system.admin

Is this role granted to the average user/tester or does it require a user with elevated permissions?

What I am noticing is that in For AWS, I am able to register the new seismic-dms tenant, where else

For IBM and Azure, I am not able to do that. I get the message - [seismic-store-service] The tenant name must match the data partition ID 'opendes'

For GCP - I have to pass the id_token instead of access_token and when I do that I get the message - [entitlement-service] 401 - "{"code":401,"reason":"Obtaining user info issue","message":"Not valid token provided"}" - appears that when I pass the id_token, the entitlement API is running into problem and if I pass the access_token then I get Unexpected token k in JSON at position 0

@ChrisZhang @manishk @anujgupta @Kateryna_Kurach @Wibben @sacha

Assignee
Assign to
Time tracking