How I used Choreo API Manager to make one OpsPulse endpoint public and keep incident records behind OAuth 2.0.
By Dimesh Methsara Opanayaka
View the OpsPulse project on GitHub
One of my OpsPulse tests returned HTTP 200 OK and "overallStatus": "Down" in the same response. Both were correct. The gateway had delivered the status report successfully. The report itself said that a simulated service was down.
That response captured the design question behind OpsPulse, an incident-management API I built with ASP.NET Core. Anyone checking a status page should be able to answer “Is there a problem?” Reading the incident records behind that answer, or opening a new incident, requires a different level of access. I wanted to see how precisely I could draw that line in Choreo API Manager.
The decision hiding inside a wildcard
I started with a local API called OpsPulseAPI . My ASP.NET Core service listened on port 5080 , and clients called the API Manager gateway over HTTPS on port 8243 .…