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

POST and GET endpoints for issuer,verifier,schema,namespace,assurance… #6

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from

Conversation

vsvishalsharma
Copy link

@vsvishalsharma vsvishalsharma commented Jul 19, 2024

New Features

  1. Governance Authority Management

    • Create new governance authorities
  2. Organization Onboarding

    • Onboard issuers with support for existing and new schemas
    • Onboard verifiers
  3. Schema Management

    • Create and retrieve schemas associated with governance authorities
  4. Namespace and Assurance Level Management

    • Create and retrieve namespaces
    • Create and retrieve assurance levels
  5. Entity Management

    • Retrieve detailed entity information
    • Fetch entity authorizations (placeholder implementation)

Note

  • The attributes field for verifiers is optional for now need to have schema reolution logic for it

Related issue #3

@vsvishalsharma vsvishalsharma force-pushed the Trust-Registry-API branch 2 times, most recently from 0491096 to 09ae462 Compare July 19, 2024 09:14
@vsvishalsharma
Copy link
Author

vsvishalsharma commented Aug 10, 2024

Changes Implemented:

  • Dropped Registry Relation Table

    • Removed the Registry Relation table as part of the schema optimization process.
  • Added Related Registry Field in Governance Authority

    • Introduced a new field in the Governance Authority table to directly reference the associated Registry, improving data integrity and simplifying queries.
  • Added Service Endpoint in Governance Authority

    • Included the serviceEndpoint field in the Governance Authority schema, ensuring each authority has a designated HTTPS URI, aligning with the [TRSP-*] requirements.
  • Added Entity Authorization

    • Incorporated the AuthorizationStatus feature, enabling control over entity access and permissions within the Trust Registry.

@vsvishalsharma
Copy link
Author

vsvishalsharma commented Sep 9, 2024

After Refactoring we have These routes

Public Routes

  1. Create Trust Registry
    • POST /
    • Creates a new trust registry.

Protected Routes (Require JWT Authentication)

  1. Onboard Issuer

    • POST /onboard-issuer
    • Onboards a new issuer.
  2. Onboard Verifier

    • POST /onboard-verifier
    • Onboards a new verifier.
  3. Create Namespace

    • POST /namespace
    • Creates a new namespace.
  4. Create Assurance Level

    • POST /assurance-level
    • Creates a new assurance level.
  5. Create Schema

    • POST /schema
    • Creates a new schema.

Public Routes for Fetching Data

  1. Get Schemas by Governance Authority

    • GET /:governanceAuthorityDid/schemas
    • Fetches schemas associated with a specific governance authority.
  2. Get Namespaces

    • GET /:registryDid/namespaces
    • Fetches namespaces under a specific registry.
  3. Get Assurance Levels

    • GET /:registryDid/assurance-levels
    • Fetches assurance levels for a specific registry.
  4. Get Entities

    • GET /:registryDid/entities
    • Fetches entities within a registry, optionally filtered by type.
  5. Get Entity Authorization

    • GET /entities/:entityDid/authorization
    • Fetches authorization details for a specific entity.
  6. Get Entity by DID

    • GET /did/:did
    • Fetches details of an entity by its DID.
  7. Get All Governance Details

    • GET /registry
    • Fetches all governance-related details across registries.

###Note
registrydid is same as governanceauthoritydid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant