Sunbird RC
v2.0.0
v2.0.0
  • Learn
    • Introduction
    • Sunbird RC Overview
      • Why do we need Sunbird RC?
      • Core Capabilities
      • Core Registry Verbs
      • Workflows
      • What Sunbird RC is and what it's not? (WIP)
      • Possibilities
      • Demo Links
    • Technical Overview
      • Registry
        • High-Level architecture
        • Technical Specification Draft
        • Tech Stack and Requirements
      • Credentialling
        • High-Level Architecture
        • Technical Specification Draft
        • Tech Stack and Requirements
    • Adopters
    • Roadmap
  • Use
    • Getting started
      • Pre-requisites
      • Install Sunbird-RC
    • Developer's Guide
      • Functional Registry
        • Installation Guide
          • Registry CLI
            • Setup A Registry Instance
          • Manual installation through docker-compose
          • Production setup through Helm
        • Working with Source Code
        • Configurations
          • Frontend Configurations
          • Frontend - Proxy configuration
          • Audit Configuration
          • Notifications Configuration
          • View Templates Configuration
        • Schema Setup
          • Introduction To Schemas
          • Creating Your Own Schemas
          • Schema Configuration
          • Create Schemas With Custom Password
        • Setup the Backend
        • Setup the Frontend
        • Backup and Restore
          • PostgreSQL
            • SQL Dump
            • File System Level Backup
            • Continuous Archiving and Point-in-Time Recovery (PITR)
          • Cassandra
            • Snapshot-based backup method
            • Incremental backup method
            • Data Restore
        • Generic Identity And Access Management
        • Metrics
        • Custom Keycloak Build
        • Custom QR Code design
        • VC Verification Module
      • Credentialling Services
        • Installation Guide
          • Run for development
          • Docker compose based
          • Helm based
        • Configurations
        • Working with the Vault
    • Integrations
      • SSO with existing systems
      • Digilocker Meripehchaan SSO
      • Digilocker Integration
    • Connectors
      • G2P Connect
      • Open ID for Verifiable Credentials (OID4VCI)
    • Release Notes
      • Registry
      • Credentialling
    • Admin Portal
      • Login
      • Get Started
        • Create Schema
        • Attestation Workflows (WIP)
        • VC Template
          • Custom VC Template (WIP)
        • Ownership (WIP)
        • Publish (WIP)
      • Dashboard
  • API Reference
    • Registry APIs
      • Registry
        • Using The APIs
        • Create An Entity
        • Invite An Entity
        • Generate token
        • Generate admin token
        • Get An Entity
        • Get An Entity By Id
        • Update An Entity
        • Create A Property Of An Entity
        • Update A Property Of An Entity
        • Revoke a Credential
        • Delete An Entity
      • Schema
        • Create Schema
        • Get Schema
        • Update Schema
        • Delete Schema
        • Publish A Schema
      • Attestation API
        • Raise An Attestation
        • Get Attestation Certificate
      • Claims API
        • Get All Claims
        • Get Claim by ID
        • Attest A Claim
      • Discovery API
        • Search An Entity
      • File Storage API
        • Upload A File
        • Get Uploaded File
        • Delete A File/ Multiple Files
      • Metrics APIs
        • Get Count
        • Get Aggregates
    • Credentialling APIs
      • Identity Service APIs
      • Credential Schema APIs
      • Credential Issuance APIs
    • Other APIs
      • Sign API
      • Verify API
      • Swagger JSON API
      • Health API
  • Reference Solutions for Functional Registries
    • Education
      • Education Ecosystem
        • Installation
      • Education Registries
        • Installation
        • User Guide
    • Health Registries
      • Organ Registries
        • Frontend Setup
        • Backend Setup
        • User Guide
      • Health Facility Registry
    • Govt to Person (G2P)
  • Reference Solutions for Digital Credentials
    • Certificate Issuance
      • Installation(WIP)
      • User Guide
    • eLocker
      • High Level Diagram
      • Installation (WIP)
        • Frontend Setup E-locker
      • User Guide
    • Vaccination Platform
    • Skills & Work Credentials
    • Unified Learners Passport (ULP)
      • ULP Capabilities
      • Example Scenario
      • Technical Components (WIP)
      • Demo/Sandbox Links (WIP)
      • Installation Guide (WIP)
        • Frontend Setup
        • Installation through docker-compose
        • Dummy records setup for refrence
  • Links
    • Source Code
    • Releases & Changelogs
    • Website
    • Roadmap
    • Reference links
    • Design
  • Community
    • Discussion Forum
    • Contributors
    • Contributing
    • Contribution Guidebook
    • Code of Conduct
    • Community Events
    • Status By Track
  • HELP
    • Roadmap
    • FAQs
    • Glossary
    • Guide to Electronic Registries and Verifiable Credentials
      • Verifiable Credentials
        • What issues will Verifiable Credentials address?
        • What are the key roles in Verifiable Credentials?
        • What are the components of Verifiable Credentials?
        • What are the benefits of Verifiable Credentials?
        • Digital Credentials vs Verifiable Credentials
        • QR code vs Verifiable QR code
        • Use Cases
      • Electronic Registries
        • Evolution of Electronic Registries
        • What issues will Electronic Registries address?
        • Benefits of Electronic Registries
        • Registry vs Database
        • Design Principles
        • Use Cases
      • Leveraging Existing data stores
    • External Open Source Software Attributions
Powered by GitBook

Copyright (c) 2023 EkStep Foundation under MIT License

On this page
Edit on GitHub
  1. Reference Solutions for Digital Credentials
  2. Unified Learners Passport (ULP)

Example Scenario

As an example scenario, consider a case of an NGO distributing textbooks to students in classes 1-5 of government schools in a State. In this scenario:

  • The school acts as the issuer, responsible for certifying the eligibility of students to receive textbooks.

  • The students are the learners who require credentials certifying their eligibility.

  • The NGO serves as the verifier, responsible for verifying the credentials and facilitating the distribution of books based on the verification result.

In this example activity, the school issues a credential certifying a student's eligibility to receive textbooks. The NGO verifies the credential using ULP's verification capability. Based on the verification result, the NGO carries out the activity of distributing books to the eligible students.

Scenario 1:

Sharan is a School Student (HOLDER) who is moving to a different city and is switching schools at the start of the academic year. The new school’s management has asked for a transfer certificate which is to be issued by the previous school’s principal. In the current scenario, Sharan has to physically go back to his school, provide a written request for a transfer certificate. The certificate is physically issued to Sharan by the school principal. Sharan then goes to his new school and submits the transfer certificate to the management. The management has employed staff members to verify the truthfulness of the transfer certificate. They do so by doing a background check at the previous school. Sharan required a week of effort to get admission into his new school.

With ULP, Sharan (Holder) can request the principal (Issuer) to issue a verifiable credential as a transfer certificate. The principal enters the data of Sharan in the portal and issues the transfer certificate as a verifiable credential. The credential is stored in Sharan’s student wallet which he can access by logging into his account. He then downloads and shares the transfer certificate to the School Management (Verifier). The School Management scans the QR Code in the verifiable credential and gets confirmation that it is a valid transfer certificate. The whole process can be completed in a day.

Scenario 2:

Monica has completed a certification course with XYZ Education. She has applied for a job opportunity with Verify Technologies who have mandated the certification from XYZ Education as a criterion. Monica received a physical certificate from XYZ Education which has an organisation seal on it with a certificate no. Monica scans the certificate and shares it with Verify Technologies to initiate the process for employment. Verify Technologies on receiving the certificate, contacts XYZ Education with name and certificate no to confirm. XYZ Education then checks the certification authenticity and informs Verify Technologies that it is valid. Monica’s interview was scheduled 1 week after initiating application.

With ULP, XYZ Education issues a certificate as a verifiable credential to Monica immediately after completion of the course. Monica during her application process with Verify Technologies shares the verified credentials. Verify Credentials verifies the authenticity of the certificate by scanning the QR Code. The interview was scheduled the next day after completion of verification.

PreviousULP CapabilitiesNextTechnical Components (WIP)

Last updated 1 year ago