FAQs
Last updated
Last updated
Who is responsible for developing and maintaining Sunbird RC?
Sunbird RC is available under the MIT open-source license. All components included in Sunbird RC are developed as open-source and are freely accessible to anyone across the globe. This project is maintained by EkStep Foundation, India.
Can an entity self-host it ? What support is available to facilitate the process?
Yes, It is possible for the entities to host Sunbird RC on their own, thereby retaining complete control over the data. The implementation of Sunbird RC can be completed in just 6 to 8 weeks, and consulting and system integrator organizations can be engaged to assist with the installation, configuration, operation, monitoring, and management of the system. The detailed provided outlines the necessary steps and configurations required for setting up and implementing Sunbird RC.
How can countries/organizations benefit from this?
Sunbird RC offers entities the freedom to utilize, manage, and distribute the platform as they wish, without any restrictions on modifications or distribution. This flexibility allows entities to tailor the software to their specific needs and deploy it at scale to benefit their citizens/users.
Can we use only Verifiable Credentials component of Sunbird RC?
Yes, it is possible as credentialing is a specific and independent microservice and it can function autonomous from the registries.
What makes Sunbird RC verifiable credentials secure and tamper-proof?
Two methods have been implemented in the underlying architecture to ensure the security and integrity of the QR code. The first method involves compressing the QR data payloads using popular compression models to make the QR size manageable for wider readability among verifier applications. Verifier applications are required to decompress the signed QR payloads in order to access the message content. The second method involves digitally signing the QRs using cryptographic keys generated via a PKI technology that uses RSA or ECDSA algorithms. Adopter countries have the option to determine the distribution channels of the "public key" with verifiers to enable them to verify the authenticity of the signed QR code. These two approaches provide the necessary layer of security to prevent unauthorized entities from tampering with the QR content.
Can the credentials issued by Sunbird RC be in multiple languages?
Yes, Sunbird RC supports the issuance of credentials in multiple languages. Organizations/Countries can provide their citizens with credentials that are localized to their language of choice.
Are the credentials issued by Sunbird RC usable offline?
Yes, the credentials issued by Sunbird RC are usable offline.
Does Sunbird RC support bulk issuance of credentials via file upload?
To facilitate the issuance of credentials in bulk, a dedicated bulk API has been developed that enables organizations to issue a large number of credentials at once. This API is not directly integrated with Sunbird RC, but instead, we have built a middleware or BFF (backend for frontend) service that acts as an intermediary between the bulk API and Sunbird RC.
How much time it takes to get a test instance of RC up and running it?
If you already have the necessary schemas prepared, configuring RC should be a relatively quick process, possibly taking only a few hours. The docker compose file is readily accessible for this purpose.
The process of defining the schemas is similar to designing a database or entity-relationship model. It involves starting with identifying the entities and their relationships, determining the actions or flows that need to be supported, and ultimately specifying the fields for each entity.
Do the private fields get stored as encrypted format?
We can encrypt the private data, but the encryption service is not provided by default in the package.
Is there a sandbox environment available for testing the Sunbird RC registry engine and API handshakes?
Yes, Sunbird RC provides a number of sandboxes and demos that are available for testing and familiarizing with the platform's capabilities. These sandboxes can be found in the "SAMPLES" section of the Sunbird RC documentation website and include a variety of use cases and scenarios.
Do we have the deployment scripts for running the instance in a Kubernetes cluster?
How are the security and privacy concerns handled when working with verifiable identity?
Sunbird RC uses Verifiable Credentials (VCs) which are signed by asymmetric keys, ensuring that only the public key is shared publicly. This provides a high level of security and privacy, as the private key is kept confidential and is used only by the credential holder to prove their identity when required.
How can I follow updates?
Sunbird RC provides multiple channels through which you can follow updates and stay informed about the latest developments. These channels include:
How can I contribute/participate?
Sunbird RC welcomes contributions from the community. There are several ways in which you can contribute, including:
Contributing to the core registry: If you have experience with software development, you can contribute to the core registry by submitting bug fixes, code improvements, or new features. You can do this by submitting a pull request on the Sunbird RC GitHub repository.
Improving documentation: Another way to contribute to Sunbird RC is by improving the documentation. This can include updating existing documentation, adding new sections, or improving the clarity and accuracy of the documentation.
Yes, we can treat the Sunbird-registry as a master registry (a layer above the source databases), which is updateable (hence, “live” at all times) by any approved changes in the source databases. However, what constitutes an “update” and how should a “change in the source database” result in an “update” in the master-registry is determined by the business processes & rules established by the program. Technically, this is feasible.
Yes, this can be done through scripts that allow bulk import of the source data into the registry.
Yes, since Sunbird RC supports defining a registry schema using a JSON Schema format, the properties can be defined with validations like mentioned here: https://json-schema.org/draft/2019-09/json-schema-validation.html#:~:text=JSON%20Schema%20validation%20asserts%20constraints,descriptive%20metadata%20and%20usage%20hints.
Yes, the Sunbird RC UI supports the generation of dynamic forms, based on the schema created; as well as support creating “approval” workflows to aid the attestation & subsequent persistence of the “data” into the registry.
No, it doesn't support versioning now. This needs to be handled manually outside Sunbird RC 2.
Yes, field and user interface level validations can be defined.
The schema needs to be created first, before seeding the data to the registry
What databases can be used for Registry?
The registry requires a main DB that is used as the main store for storing all data. The following DB providers can be used:
Graph database (Neo4J)
Relational databases (Postgresql, HSQLDB, H2, MariaDB, MySQL, MSSQLServer)
NoSQL databases (Cassandra)
In dev/local setup, it is required that keycloak hostname is added to '/etc/hosts' file.
API documentation for generating the token is available here, Generate token Generate admin token
If the above steps did not resolve the problem, please follow the next steps provided.
Goto the registry container / docker-compose and identify the value set for sunbird_sso_url . Copy the value for further user.
Goto keycloak admin console and select the realm Ex:sunbird rc (if no new realm was created) and goto Realm Settings
Paste the value copied in Frontend URL text box
Click on Save
If your url is not secure / doesn't have a SSL, goto login tab, select none for Require SSL and click on Save
Restart the registry
Yes, Sunbird-RC supports “user login” and also ownership management for a schema. Hence if the registry needs to have “citizen” access; it can be enabled. Just a point to reiterate, the purpose of a registry can be non-individual centric as well (in which case, the authorized “user”, can be institutional staff roles as well).
Can we we use single sign on? or use any other authentication?
Currently, Sunbird works on Keycloak OAuth. However, we can write a custom service to authenticate the user, with other authentication methods.
Currently, consent is given by an individual to the entities that he/she has ownership of (i.e. to the entities which were created by him/her). Consent can be given to one or more attributes that are part of the schema.
Currently, consent can only be revoked manually. For time/count-based revocation of consent, we need to build a custom service to handle it.
Yes, attestation can be done with an external system. We need to write the functionality to enable data exchange between these two systems.
We have three services that uses Postgres**.**
Keycloak: Data related to user management, client management, realm management, consent etc will be stored
Registry core: All data created under the schemas will be stored.
Claims: All data related to attestation flows(claims) will be stored.
Sunbird RC can work on the below DBs:
Graph database (Neo4J)
Relational databases (Postgresql, HSQLDB, H2, MariaDB, MySQL, MSSQLServer)
NoSQL databases (Cassandra)
Currently, we have added custom SPI and themes to support otp based login in keycloak. If your usecase requires password based login, then the below changes need to be done in keycloak.
Changing the theme
1. Login to keycloak admin console
2. Goto Clients > registry-frontend
3. Select keycloak in Login Theme option
4. Save the changes
Update login flow
1. Login to keycloak admin console
2. Goto Authentication > Bindings
3. Select browser in Browser Flow option
4. Save the changes
In the registry, while creating/inviting an entity it throws/returns an error mentioning Role creation exception. This could be because admin-api, the client which is configured for the registry does not have the required roles. The below steps need to be configured for the same.
Goto keycloak admin console (http://keycloak-host/auth/
Login admin credentials
Goto clients tab in configure section on the left
Click on admin-api client and goto Service Account Roles tab
In Client roles drop-down, select realm-management
Make sure manage-realm is present Assigned Roles section
If not select manage-realm from Available Roles section and click on Add selected
Restart the registry service
Configure Certificate API Service:
Enable Signing in the Registry:
Sample Template:
How to resolve CORS errors on local development environment?
One of the available samples is the . This sample is designed to showcase how Sunbird RC can be used in an education context.
Yes, Sunbird RC provides deployment scripts that can be used to run the platform in a Kubernetes cluster. You can access the deployment scripts at .These scripts are designed to be easy to use and provide a streamlined deployment process for running Sunbird RC in a Kubernetes environment.
GitHub: Sunbird RC's is the primary source for technical and project management updates. You can follow the repository to receive notifications about new releases, bug fixes, and other technical updates.
Social accounts: Sunbird maintains active social media accounts on and . By following these accounts, you can receive regular updates and news about the platform, as well as insights from the Sunbird team.
GitHub Discussions and Discord: Sunbird RC has active discussion forums on and , where community members can engage with one another and discuss topics related to the platform. These forums are a great way to stay connected with the Sunbird RC community and get involved in ongoing discussions.
Reporting bugs/requesting features: If you encounter any issues while using Sunbird RC or have suggestions for new features, you can them on the project's GitHub repository. This helps the Sunbird RC team identify and address issues more quickly.
Contributing to the registry CLI: If you have experience with CLI development, you can by submitting code improvements or new features.
Use `` url to fetch the token
You can check the following registry cli All the prerequisites are mentioned here. Using this cli you will be able to bring up all the services required. The following keycloak configurations need to be configured in SB-RC.
Begin by configuring your .
The certificate template should have the handlebars parameter "{{qrCode}}" to render a qr code in the certificate. Additionally to know more about how to create a certificate template, please go through the :
Explore a sample template .
Please Refer to the link for the solution:
