[4.10] Unable to Issue Certificates for All Courses and Users

[komalm]

Hello @pallakartheekreddy,

Environment Details:

• Platform: SunbirdEd Portal
• Version: 4.10

Background:
We are currently facing an issue where users are unable to receive certificates after course completion.

Assumptions:

• This issue started occurring after the change in content/template storage location.
• Note: We have already updated the new host URL across all content/templates and the required services.
  However, despite these updates, users are still unable to receive certificates.

Issue Details:

• Users are able to enroll in and complete the courses.
• All parameters required for certificate issuance are fulfilled.
• Users are eligible for certificate generation.
• However, certificates are not getting issued automatically.
• We also attempted to manually trigger certificate re-issuance, but it was unsuccessful.
• Upon checking the logs in the certsign service, we observed the following error:

batchId: '{{batchId}}',
    type: 'Course'
  },
  osUpdatedAt: '2025-04-25T09:56:59.676Z',
  osUpdatedBy: 'anonymous',
  recipient: {
    osid: '1-f05a44f6-860a-4fdc-9fd1-179770338081',
    osUpdatedAt: '2025-04-25T09:56:59.676Z',
    osCreatedAt: '2025-04-25T09:56:59.676Z',
    osUpdatedBy: 'anonymous',
    name: '{{user name}}',
    osCreatedBy: 'anonymous',
    id: 'cfcc1849-ba80-48f6-987b-732d58e8a2f9'
  },
  signatory: [
    {
      image: 'https://cdn.pixabay.com/photo/2014/11/09/08/06/signature-523237__340.jpg',
      osUpdatedAt: '2025-04-25T09:56:59.676Z',
      osCreatedAt: '2025-04-25T09:56:59.676Z',
      osUpdatedBy: 'anonymous',
      name: 'NULP',
      osCreatedBy: 'anonymous',
      osid: '1-21aca527-7ea2-4ad9-83db-9faaa6aaa218',
      designation: 'CEO',
      id: 'nulp'
    }
  ],
  osid: '1-59987b18-cc20-41a4-97b3-d6345d1f3b82',
  osOwner: [ 'anonymous' ],
  templateUrl: 'https://nulpstorage.blob.core.windows.net/contents/content/do_11408950391347609611388/artifact/do_11408950391347609611388_1719910146008_sample_cert-2sign-1-logo.svg',
  osCreatedAt: '2025-04-25T09:56:59.676Z',
  certificateLabel: '{{certificateLabel}}',
  osCreatedBy: 'anonymous',
  issuer: {
    osid: '1-38432fa5-e30d-443d-bc9d-d775e5e4e0ed',
    osUpdatedAt: '2025-04-25T09:56:59.676Z',
    osCreatedAt: '2025-04-25T09:56:59.676Z',
    osUpdatedBy: 'anonymous',
    kid: 'def05b22-4367-4017-ab15-f11d5942d42f',
    name: '{{name}}',
    osCreatedBy: 'anonymous',
    url: 'https://org_site.org/'
  },
  status: 'ACTIVE'
}
Sending {
  '@context': [
    'https://www.w3.org/2018/credentials/v1',
    'https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json',
    'https://nulpstorage1.blob.core.windows.net/contents/schema/sunbird_context.json'
  ],
  type: [ 'VerifiableCredential' ],
  id: 'did:sunbird:1-59987b18-cc20-41a4-97b3-d6345d1f3b82',
  issuanceDate: '2025-04-25T09:56:59.676Z',
  credentialSubject: {
    type: 'NMCG certificate',
    recipientName: '{{user name}}',
    trainingName: '{{course name}}',
    trainingId: 'do_1136550052517314561308'
  },
  issuer: {
    id: 'https://raw.githubusercontent.com/project-sunbird/sunbird-devops/release-4.8.0/kubernetes/helm_charts/sunbird-RC/registry/templates/READ.md#Issuer',
    type: [ 'Issuer' ],
    name: 'NULP',
    url: 'https://org_site.org/',
    publicKey: [ '{{publicKey}}}' ]
  }
}
checking https://www.w3.org/2018/credentials/v1
checking https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json
Fallback url lookup for document :https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json
jsonld.InvalidUrl: Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.
    at ContextResolver._fetchContext (/app/node_modules/jsonld/lib/ContextResolver.js:159:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ContextResolver._resolveRemoteContext (/app/node_modules/jsonld/lib/ContextResolver.js:114:34)
    at async ContextResolver.resolve (/app/node_modules/jsonld/lib/ContextResolver.js:47:22)
    at async api.process (/app/node_modules/jsonld/lib/context.js:64:20)
    at async api.expand (/app/node_modules/jsonld/lib/expand.js:209:17)
    at async Function.jsonld.expand (/app/node_modules/jsonld/lib/jsonld.js:339:18)
    at async Function.jsonld.toRDF (/app/node_modules/jsonld/lib/jsonld.js:669:16)
    at async Function.jsonld.normalize.jsonld.canonize (/app/node_modules/jsonld/lib/jsonld.js:578:19) {
  details: {
    code: 'loading remote context failed',
    url: 'https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json',
    cause: JsonLdError [jsonld.LoadDocumentError]: URL could not be dereferenced, an error occurred.
        at loadDocument (/app/node_modules/jsonld/lib/documentLoaders/node.js:72:13)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at async RequestQueue.add (/app/node_modules/jsonld/lib/RequestQueue.js:33:14)
        at async ContextResolver._fetchContext (/app/node_modules/jsonld/lib/ContextResolver.js:152:19)
        at async ContextResolver._resolveRemoteContext (/app/node_modules/jsonld/lib/ContextResolver.js:114:34)
        at async ContextResolver.resolve (/app/node_modules/jsonld/lib/ContextResolver.js:47:22)
        at async api.process (/app/node_modules/jsonld/lib/context.js:64:20)
        at async api.expand (/app/node_modules/jsonld/lib/expand.js:209:17)
        at async Function.jsonld.expand (/app/node_modules/jsonld/lib/jsonld.js:339:18) {
      details: [Object]
    }
  }
}

• Based on the logs, the error is occurring while trying to access:

https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json

• The issue appears because the URL still points to the old host, which is now inaccessible.
• Additionally, in the payload sent for certificate signing, we noticed that the @context contains old URLs:

    "@context": [
      "https://www.w3.org/2018/credentials/v1",
      "https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json",
      "https://nulpstorage1.blob.core.windows.net/contents/schema/sunbird_context.json"
    ]

• The host in these schema URLs has not been updated to the new storage location.

Request for Support:
Could you please guide us on the necessary steps to update the schema URLs used in certificate generation?
Is there any additional configuration or migration step required in the certsign service or certificate issuance templates?

We would appreciate your support in resolving this issue.

cc @jona-r, @manishakapadnis, @vinod303

[NIUANULP]

@madhucr @pramodkvarma
We're reaching out regarding an ongoing issue with the National Urban Learning Platform (NULP). Our users are currently not receiving their certificates. Despite our efforts over the past few days, we’ve encountered the challenges outlined above and have been unable to resolve them.

[madhucr]

@NIUANULP Will have someone look into it.

[pallakartheekreddy]

@madhucr Sure. We already have another email thread going on with the team(Komal and Team) regarding this issue. We didn’t update here because we haven’t found the root cause yet.

[aimansharief]

@pallakartheekreddy We found that there was a hardcoding inside this file
https://nulpstorage1.blob.core.windows.net/contents/schema/v1_context.json
@komalm As discussed in the call please update the right values, and let us know if you face any further issues.

[komalm]

The issue has been successfully resolved after updating the credential_template.json file.

During the investigation, we found that the template was referencing outdated or incorrect storage paths, which caused the certificate generation to fail. After correcting the storage path references in the credential_template.json and redeploying the updated configuration, the system is now functioning as expected.

Thank you to the @pallakartheekreddy and @aimansharief for your prompt support throughout the troubleshooting process.