Queryable Encryption Azure KMS

Wilmer_Caiza · 2025-02-06T15:34:59.043Z

Hello,

I’m trying to implement Queryable Encryption with both automatic and explicit encryption. My KMS is configured on Azure.

However, when I attempt to configure MongoDB Compass with the ‘In-Use Encryption’ connection option, I encounter an error.

I’m new to this feature. Could you please provide some guidance?

Error parsing JSON in KMS response 'Got parse error at "<", position 0: "SPECIAL_EXPECTED"'. HTTP status=404. Response body= <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> <title>404 - File or directory not found.</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;} fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF; background-color:#555555;} #content{margin:0 0 0 2%;position:relative;} .content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} --> </style> </head> <body> <div id="header"><h1>Server Error</h1></div> <div id="content"> <div class="content-container"><fieldset> <h2>404 - File or directory not found.</h2> <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3> </fieldset></div> </div> </body> </html>```

Joel_Odom · 2025-02-06T16:51:05.930Z

Hi and welcome to our forums. I’m a PM for QE, not Compass, but it looks like one of the Azure parameters is incorrect, based on the response from the server. Can you provide the parameters you’re using below (and redact the password, at least).

image632×808 36.1 KB

Wilmer_Caiza · 2025-02-10T16:28:06.305Z

Thanks for responding,

I was able to resolve the issue, looks like I set up a wrong Identity Platform Endpoint, after remove it works fine.