krb5-server

krb5-server appears to provide a Kerberos 5 (krb5) server component/service for issuing and validating Kerberos tickets (authn) in a networked environment. It is intended for deploying Kerberos KDC/auth services rather than as a client library.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ Security kerberos authentication kdc realm infrastructure security
⚙ Agent Friendliness
3
/ 100
Can an agent use this?
🔒 Security
42
/ 100
Is it safe for agents?
⚡ Reliability
0
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
0
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
80
Scope Granularity
20
Dep. Hygiene
50
Secret Handling
30

Kerberos typically provides strong authentication, but server deployments rely on secure keytab/secret management, correct crypto configuration, and strict network controls. No evidence about TLS usage, dependency posture, or secret-handling practices was included in the supplied content.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
0
AF Security Reliability

Best When

When you need to run or host Kerberos KDC/related services within a controlled network/realm and can manage Kerberos configuration, principals, and keys.

Avoid When

When you need a turnkey SaaS API, web-based auth endpoints, or you cannot securely manage Kerberos keys/secrets and realm configuration.

Use Cases

  • Internal enterprise authentication using Kerberos (KDC/realm services)
  • Service-to-service authentication in environments standardized on Kerberos
  • Setting up or running a Kerberos infrastructure component for existing clients/services

Not For

  • Public internet-facing authentication endpoints without additional network controls
  • Use cases requiring OAuth/SAML-style web SSO flows
  • Applications that only need Kerberos client-side ticket acquisition and not a server component

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: Kerberos protocol (ticket-based authentication)
OAuth: No Scopes: No

Authentication is inherent to Kerberos (tickets/service principals). Specific auth mechanisms, supported transports, and any admin interfaces are not provided in the supplied information.

Pricing

Free tier: No
Requires CC: No

No pricing information was provided; this appears to be self-hosted software.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Kerberos server software is configuration- and key-management heavy; agent attempts to automate changes may fail without correct realm/KDC configuration.
  • Protocol and operational failures can be environment-specific (DNS, clock skew, firewall ports, keytab permissions), so generic automation may produce non-obvious errors.
  • No programmatic interface (REST/SDK/MCP) is evidenced from the provided info, so an agent may not be able to interact safely/consistently without operating-system level access.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for krb5-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered