Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C connection-manager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Gaia-X
  • Organization Credential ManagerOrganization Credential Manager
  • connection-manager
  • Issues
  • #6
Closed
Open
Issue created Feb 22, 2022 by Sagar Khole@sagar.kholeDeveloper

Agent Accept a stored connection invitation status

Description

This API returns the current status of connection between Principal and Participant to the Connection Manager.

  • AFJ agents call the API with configured webhook URL when the status is changed.

Status can be:

  • Invited,
  • Requested,
  • Responded,
  • Complete.

Update connection status API.

  • Endpoint: POST /v1/connections

Libraries

  • nats
  • @nestjs/microservices

Expected Input

{
            "id": "265160e1-12f6-4b76-8bff-2d239c83b4de" ,
            "state":  'complete',
            "did":  'PNZyZVh8hcC3goEiu79CQJ',
            "theirDid": '9YKWf1VQJT857ZkaPd3E1y',
            "theirLabel": 'invitee'
}

Expected Output

  • The connection Should be updated as the status changed agent side and it should reflect in the connection table.
{
  statusCode: 200,
  message: 'Connection status Updated successfully',
  data: {
    id: '0e15d082-96ff-428b-ba4b-d9cdcb640e7a',
    connectionDate: 2022-03-09T11:46:33.020Z,
    createdDate: 2022-03-09T11:46:33.020Z,
    updatedDate: 2022-03-09T11:47:37.636Z,
    connectionURL: '',
    did: 'GYnXcAftprWFD8r1PnkG2n',
    status: 'complete',
    connectionId: '2730c1c8-49d6-433e-afc5-764983d73c5b',
    theirDid: 'G13tqkTj7PzBvEPq2UBXuN',
    theirLabel: 'invitee'
  }
}

Steps to test

  • The requested input should be in standard format for all the fields.
  • Response should show the accurate status code and applicable message.
  • Required parameters exceptions handled with the accurate status code and applicable message

Dependencies

  • NA

Blocker

  • NA
Edited Mar 11, 2022 by Akshay Gadekar
Assignee
Assign to
Time tracking