|
| 1 | +--- |
| 2 | +title: "Dev Proxy v2.3.1 with fixes for permissions guidance and Entra mocking" |
| 3 | +description: "Dev Proxy v2.3.1 fixes GraphMinimalPermissionsGuidancePlugin not evaluating all application endpoints and EntraMockResponsePlugin crashing on startup." |
| 4 | +date: 2026-04-14 |
| 5 | +author: "Waldek Mastykarz, Garry Trinder" |
| 6 | +tags: ["release"] |
| 7 | +image: "/blog/images/v2-3-1.png" |
| 8 | +--- |
| 9 | + |
| 10 | +We've just released **Dev Proxy v2.3.1** - a patch release that fixes two bugs affecting permission analysis and Entra ID mocking. |
| 11 | + |
| 12 | +### **In this version:** |
| 13 | + |
| 14 | +- Fixed **GraphMinimalPermissionsGuidancePlugin** not evaluating all application endpoints |
| 15 | +- Fixed **EntraMockResponsePlugin** crashing on startup |
| 16 | + |
| 17 | +### **Fixed permissions guidance for application endpoints** |
| 18 | + |
| 19 | +If you use the **GraphMinimalPermissionsGuidancePlugin** to check which application permissions your app actually needs, you might have run into a bug where only the first Microsoft Graph endpoint was evaluated. The rest were silently skipped, and you'd see "No permissions found" in the output: |
| 20 | + |
| 21 | +``` |
| 22 | + info Evaluating application permissions for: GET /groups |
| 23 | + fail Couldn't determine minimal permissions for the following URLs: - (No permissions found.) |
| 24 | +``` |
| 25 | + |
| 26 | +The root cause? The plugin coupled collecting endpoints with capturing role claims from the access token. Once it captured roles from the first request, it stopped adding subsequent endpoints to the evaluation list. |
| 27 | + |
| 28 | +**What changed:** |
| 29 | + |
| 30 | +We decoupled endpoint collection from role capture. Every application-typed Microsoft Graph request is now added to the evaluation list, regardless of when roles are first encountered. The result: all your Graph API calls are properly analyzed for minimal permissions. |
| 31 | + |
| 32 | +### **Fixed EntraMockResponsePlugin startup crash** |
| 33 | + |
| 34 | +Starting Dev Proxy with **EntraMockResponsePlugin** enabled caused an immediate crash on all v2.x versions: |
| 35 | + |
| 36 | +``` |
| 37 | +fail An error occurred while running Dev Proxy |
| 38 | +Exception Details: System.InvalidOperationException: Unable to resolve service |
| 39 | +for type 'System.Security.Cryptography.X509Certificates.X509Certificate2' |
| 40 | +while attempting to activate 'DevProxy.Plugins.Mocking.EntraMockResponsePlugin'. |
| 41 | +``` |
| 42 | + |
| 43 | +The plugin tried to resolve the root certificate during construction - before the certificate was registered in the dependency injection container. If you were mocking Entra ID token endpoints, Dev Proxy wouldn't even start. |
| 44 | + |
| 45 | +**What changed:** |
| 46 | + |
| 47 | +The plugin now resolves the certificate on demand, when it's actually needed to process mock responses, rather than during startup. No more crashes, and your Entra ID mocking configurations work as expected. |
| 48 | + |
| 49 | +## Dev Proxy Toolkit |
| 50 | + |
| 51 | +[Dev Proxy Toolkit](https://marketplace.visualstudio.com/items?itemName=garrytrinder.dev-proxy-toolkit) is an extension that makes it easier to work with Dev Proxy from within Visual Studio Code. Alongside the new release of Dev Proxy, we've also released a new version of the toolkit, v1.18.0. |
| 52 | + |
| 53 | +In this version, we've: |
| 54 | + |
| 55 | +- Updated all JSON snippets to use v2.3.1 schemas |
| 56 | + |
| 57 | +Checkout out the [changelog](https://marketplace.visualstudio.com/items/garrytrinder.dev-proxy-toolkit/changelog) for more information on changes and bug fixes. |
| 58 | + |
| 59 | +### **Why upgrade to v2.3.1?** |
| 60 | + |
| 61 | +✅ **Accurate permissions analysis** - All application endpoints are now properly evaluated for minimal permissions |
| 62 | +✅ **Working Entra ID mocking** - EntraMockResponsePlugin starts reliably on all platforms |
| 63 | + |
| 64 | +### **Try it now** |
| 65 | + |
| 66 | +Download **Dev Proxy v2.3.1** today and build better API-connected applications with confidence! |
| 67 | + |
| 68 | +Got feedback or ideas? [Join us](https://github.com/dotnet/dev-proxy/discussions) and be part of the conversation. |
0 commit comments