endor-troubleshoot-authlog

Correlate AuthenticationLog records with AuthorizationPolicy configuration to diagnose tenant SSO login failures.

4|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-troubleshoot-authlog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: endor-troubleshoot-authlog
Source: https://github.com/endorlabs/endorlabs-sdk/tree/main/agent-knowledge/skills/endor-troubleshoot-authlog
Command: npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-troubleshoot-authlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose why a tenant user cannot sign in, cannot reach the right tenant, or sees authorization failures by comparing Endor Labs authentication evidence with policy configuration.

Core Features & Use Cases

  • AuthenticationLog investigation: Review login attempts, failures, and authorized tenant data to correlate IdP behavior with what Endor Labs recorded.
  • AuthorizationPolicy review: Inspect policy rows for namespace access, claim mapping, and tenant-scoped authorization problems.
  • Structured troubleshooting exports: Produce consistent investigation output for later analysis or escalation.
  • Use case: A user says they authenticated successfully but still have “no authorized tenant”; this Skill helps identify whether the issue is in the SSO claims, tenant mapping, or authorization policy.

Quick Start

Ask the skill to inspect the tenant’s authentication logs and authorization policies for a specific user or login failure and summarize the most likely cause.

Frequently Asked Questions about endor-troubleshoot-authlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot SSO login failures when a user authenticates but gets a no authorized tenant error in Endor Labs?▼

To troubleshoot SSO login failures with a no authorized tenant error, correlate the user's AuthenticationLog records against the tenant's AuthorizationPolicy configuration to identify mismatches in claim-to-namespace mapping or policy access rules.

What causes claim-to-namespace mapping issues during tenant SSO authentication?▼

Claim-to-namespace mapping issues during tenant SSO authentication occur when the identity provider claims sent during login do not align with the namespace access rules defined in the Endor Labs AuthorizationPolicy, causing tenant authorization failures.

How do I inspect Endor Labs authentication logs to diagnose an SSO incident?▼

Inspect Endor Labs authentication logs by listing tenant-scoped AuthenticationLog records for the affected user, reviewing login attempt outcomes, and comparing the recorded identity provider behavior against the active AuthorizationPolicy configuration.

Can I export structured troubleshooting data for an Endor Labs authentication incident review?▼

Yes, you can export structured troubleshooting data for an Endor Labs authentication incident review by generating a JSON export of the correlated AuthenticationLog and AuthorizationPolicy findings for reproducible analysis and escalation.

Why does a successfully authenticated user still experience tenant authorization failures?▼

A successfully authenticated user experiences tenant authorization failures when the SSO claims delivered by the identity provider do not satisfy the specific tenant mapping or namespace access rules enforced by the Endor Labs AuthorizationPolicy.