New in Grafana 9.1: Service accounts are now GA

Grafana 9.1 has introduced service accounts as generally available, enhancing machine-to-machine interactions by allowing automated or compute workloads to interact with Grafana's APIs securely and efficiently. Service accounts are linked to organizations rather than individual users, facilitating easier management and token rotation without the need to change tokens when administrators leave. They are designed to minimize permission sprawl by allowing specific roles and permissions tailoring, which reduces the risk of compromising the system. The new system also supports the migration of existing API keys to service accounts, enabling multiple tokens per account for better token management and security. Service account tokens now have a visually identifiable pattern with a "glsa" prefix and a checksum to help developers recognize and verify tokens in codebases, reducing false positives in open source secret scanners. The Grafana AuthNZ team plans to continue enhancing authentication and authorization features to bolster security in Grafana, with comprehensive documentation available for those interested in implementing service accounts.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.