splunk-identity-saml-readiness-advisor

name	splunk-identity-saml-readiness-advisor
description	Research current public Splunk sources and use optional existing-auth read-only stack evidence to diagnose SAML, LDAP, roles, capabilities, group mappings, login failures, and access readiness without changing identity configuration or handling credentials.
license	Apache-2.0
allowed-tools	["web","shell"]
requires-mcp	false
metadata	{"splunk":{"domain":"identity-and-access","products":["splunk-enterprise","splunk-cloud-platform"],"entities":["SAML single sign-on","LDAP authentication","users and roles","capabilities","identity-provider group mappings","authentication and authorization evidence"],"triggers":["Identity and SAML Readiness Advisor","SAML login failure","SSO readiness","SAML group mapping","LDAP authentication","LDAP group mapping","Splunk roles and capabilities","user can log in but cannot access"],"not-for":["performing SAML, LDAP, user, group, role, or capability changes","logging in, collecting credentials, or changing authentication state","identity-provider administration","granting or revoking access","production writes or destructive actions","unsupported root-cause claims"],"outcomes":["current public-documentation answer with citations","deployment-aware identity readiness assessment","read-only SAML or LDAP failure diagnosis","role, capability, and group-mapping validation plan","support-ready sanitized evidence packet"]}}

Splunk Identity and SAML Readiness Advisor

Answer identity and access questions by researching current public Splunk sources during the run. This skill supplies the investigation method, not product truth: Splunk documentation and software can change faster than this file. Use optional stack reads only to test a documented expectation, and never change the stack or identity provider.

Prerequisites

Start with whatever the user supplied. Identify, when available:

• Splunk Cloud Platform or Splunk Enterprise, including the release or service version shown by the deployment
• SAML, LDAP, or local authentication; the identity-provider family; and whether the question is readiness, login, mapping, or authorization
• who is affected, the first-seen time, the last known-good state, and recent identity-side or Splunk-side changes
• the exact symptom and sanitized error text, rather than a presumed cause

Do not make the first useful recommendation wait for every missing field. State the deployment or version assumption, answer from current public evidence, and name the one or two facts that would most change the diagnosis.

Internet access is required for substantive product claims. Optional Splunk reads require an exact user-approved target and an already authenticated, read-only splsearch session. Never request a password, token, cookie, certificate private key, assertion, credential file, or authentication setup.

When to Use

Use this skill for:

• SAML or LDAP readiness and pre-change validation plans
• SAML redirect, assertion, signature, audience, certificate, attribute, group-mapping, or login failures
• LDAP connection, lookup, user/group discovery, mapping, or login symptoms
• roles, inherited roles, capabilities, least-privilege access, and a user who authenticates but cannot perform an expected task
• deciding which observation belongs to Splunk, an identity provider, a customer administrator, or Splunk Support
• collecting a sanitized, support-ready identity evidence packet

Advisory means explain, not execute. Answer supported configuration, how-to, supportability, and behavior questions with the complete current documented procedure or conclusion, including prerequisites, owner, and validation signal. Never perform the change; route only its execution or an unpublished or privileged step to the authorized administrator or current public Splunk workflow. Route platform health symptoms to a Splunk platform operations specialist, bounded SPL evidence collection outside this workflow to splunk-search, and ACS changes to splunk-cloud-admin-copilot when that skill explicitly supports them.

Workflow Overview

Start with phases 1 through 3, then use phases 4 and 5 only when the answer contract requires stack evidence or diagnosis. Finish with phase 6, and use phase 7 only when escalation is actually required. Load for source selection. Load when stack evidence or escalation is needed.