<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Grafana on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/grafana/</link>
    <description>Recent content in Grafana on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Sat, 02 May 2026 23:13:05 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/grafana/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Adding SSO to MCP Grafana Server</title>
      <link>https://www.hairizuan.com/adding-sso-to-mcp-grafana-server/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/adding-sso-to-mcp-grafana-server/</guid>
      <description>&lt;p&gt;The MCP Grafana server previously relied on static API keys or basic auth for authenticating requests to Grafana. This works fine for local development or single-user setups, but falls apart once you have multiple users who each need their own Grafana permissions. Passing around shared API keys is a security concern and means everyone operates with the same access level regardless of their actual role.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
