Fix path processing logic in addToMdocRequest

[vanhoanHoang]

Description

Currently by requesting an iso/mdoc from the Wallet resulting a wallet succesfully sending a mdoc. The received mdoc on Verifier side however does not contain any attributes requested in the presentation request. This is due to the processing logic in the addToMdocRequest function (here)

Currently, this line splits the namespace concatenated with the requested attribute using a . as the delimiter. However, for namespaces that already contain a . (such as those in mdl), this causes the claim and the namespace to be incorrectly split and then added to the MDocRequestBuilder. In case of org.iso.18013.5.1, only org is set to be the namespace. This is leading to incorrect behavior, as the full path isn't being processed as expected.

The following is one of the presentation_definition , which requests first_name in the mdl. The mdl contains given_name, family_name and other attributes:

{
   "id":"fccd9c29-c2e7-4110-b792-a87cb81c55ef",
   "input_descriptors":[
      {
         "id":"org.iso.18013.5.1.mDL",
         "purpose":"authenticate user via MDOC",
         "format":{
            "mso_mdoc":{
               "alg":[
                  "EdDSA",
                  "RSA"
               ]
            }
         },
         "constraints":{
            "fields":[
               {
                  "path":[
                     "$.docType"
                  ],
                  "filter":{
                     "pattern":"org.iso.18013.5.1.mDL",
                     "type":"string"
                  },
                  "intent_to_retain":false
               },
               {
                  "path":[
                     "$['org.iso.18013.5.1']['given_name']"
                  ],
                  "filter":{
                     "pattern":".*",
                     "type":"string"
                  },
                  "intent_to_retain":true
               }
            ]
         }
      }
   ]
}

Type of Change

• [x ] bug fix - change which fixes an issue

Checklist

• [x ] code cleanup and self-review

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud