CTK local test: Device Discovery handled but test does not proceed

Support
1

I’m currently testing CTK (Compliance Tool Kit) installed on my local machine.

After successfully launching CTK and creating a project, I implemented the test Device Discovery Response according to the MDS Specification (MDS Specification | MOSIP Docs 1.2.0).

image
image1242×700 43.5 KB

The response is captured correctly by CTK, but the process does not proceed beyond that point.

To troubleshoot, I also registered the partner and created a device in the PMP portal (under Device Details – Create Device), but the issue persists.

I would appreciate any help or guidance on how to resolve this.

Below is the Device Discovery Response data I used:

==================================================================
// cpp
resp._deviceId = “1”;
resp._deviceStatus = “Not Registered”;
resp._certification = “L0”;
resp._serviceVersion = “0.9.5”;
resp._deviceSubIdList.append(“0”);
resp._callbackId = “http://127.0.0.1”;
resp._deviceCode = “111122223333”;
resp._specVersionList.append(“0.9.5”);
resp._purpose = “Registration”;

resp._digitalId._serialNo = “111122223333”;
resp._digitalId._make = “Brand”;
resp._digitalId._model = “Model”;
resp._digitalId._type = “Iris”;
resp._digitalId._deviceSubType = “Double”;
resp._digitalId._deviceProvider = “test1111”;
resp._digitalId._deviceProviderId = “test1111”;
resp._digitalId._dateTime = “2025-07-17T11:18:12”;

resp._error._errorCode = “100”;
resp._error._errorInfo = “Device not registered”;

3

image
image1033×411 22.2 KB

I am currently trying to test a device intended for use as a registration device.

In the “Add a new Project” form, there is a required field called SBI Hash.

What does SBI Hash mean, and where can I find or generate it?

Any guidance would be appreciated.

4

image
image670×335 14.2 KB

In the Digital ID structure shown in the documentation, what does the field deviceProviderId refer to?

Is it the CTK login ID, or is it a separately assigned identifier?

I would appreciate clarification on where this ID comes from and how it should be set.

5

The main issue (device not found) has now been resolved.
It turned out to be a mistake on my end related to the Device Discovery response JSON.
I’d be grateful if you could take a look at my earlier questions regarding the SBI Hash and deviceProviderId.

6

Hi @wjyang

Thanks for reaching out.
We are looking into your query and will get back to you soon!

Until then, happy coding with MOSIP!

Best regards,
Team MOSIP

7

Hi @wjyang

You can refer here to understand SBI Hash: Hash Generation | Compliance Tool Kit

DeviceProviderId = partner id that you can get after onboarding the partner in PMS

Hope this helps.
Mayura