Menu

Zipkin has no built-in UI authentication, so exposure is an architecture decision
📰

Zipkin has no built-in UI authentication, so exposure is an architecture decision

DEV Community: authentication·yutianle·3 days ago
#b5tcsVbH
#devtoauthentication#devto#dev#zipkin#query
Reading 0:00
15s threshold

Zipkin has no built-in UI authentication, so exposure is an architecture decision

Zipkin's architecture documentation states that there is no built-in authentication in the UI. The UI queries the Zipkin API to search traces and render service maps, spans, timing, and errors. That makes Zipkin an observability service with a clear access-control requirement: if the UI is reachable, the operator must provide the missing authentication and authorization at another layer.

On 13 November 2026 at 03:46 China Standard Time, a ZoomEye count-only query with sub_type=all , page 1, and page size 1 returned 39 matches for title="Zipkin" and 559 matches for app="Zipkin" . The inversion is useful. A custom UI or proxy may change the title, and many instrumented applications can mention Zipkin without exposing the server UI.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.