Actually, our team is working on the software development on passing the MOSIP L0 device compliance test, so what we want is to start offical compliance test as soon as possible. From my current knowledge, the steps should be first setup sandbox in our local environment, and then do some software development work based on something like MDS or reg-client. Is this workflow right? or there is another way to do the complicance test without deploy whole MOSIP services on our local environment?
Since these days, our teams keeps working on deploy the MOSIP sandbox (version 1.2.0.1-B3), but we still could not bring all things up here.
We met serveal problems here, after we solve the problem mentioned in this thread. We also met the problem of pending import of MOSIP cluster into rancher (like what mentioned in this thread https://community.mosip.io/t/error-while-importing-cluster-to-rancher/597?u=andymatos), we tried the solutions mentioned, but no good. so we could not install monitor app on this cluster, and then we deicde to skip the monitor part and keep going on deploy the reset MOSIP services, however during the installation of MOSIP services, it ends with in install key manager with some error that Service Monitor not found. So we guess the Monitor part is necessary for the rest part?
Also we try the collab env, first we visit the PMP part, we could visit the link https://pmp.collab.mosip.net, but it finally end with connection timeout on visiting some urls like https://iam.collab.mosip.net/auth/realms/mosip/protocol/openid-connect/, we do not know where is the problem, we tried both with direct visit or with a speed up proxy, but both could visit the PMP part
So in sum, we want to start complience test asap, we will also keep try to bring MOSIP sandbox up on here, any help on these two things would be greatly appreciated.