ci-loopback-oidc-cert-trust

Diagnose CI-only HTTPS certificate trust failures for loopback OIDC providers.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill ci-loopback-oidc-cert-trust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-loopback-oidc-cert-trust
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/ci-loopback-oidc-cert-trust
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill ci-loopback-oidc-cert-trust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves intermittent CI failures in GitHub Actions where tests using loopback OIDC providers fail due to untrusted localhost HTTPS certificates.

Core Features & Use Cases

  • Diagnostic Framework: Provides a structured approach to distinguish between environment-specific certificate trust issues and actual application logic regressions.
  • CI Optimization: Offers specific recipes for configuring OpenSSL trust on Linux runners and managing Aspire-backed auth lanes.
  • Use Case: Use this when your local tests pass, but your GitHub Actions pipeline fails with AuthenticationException: UntrustedRoot during OIDC token exchange.

Quick Start

Apply the ci-loopback-oidc-cert-trust diagnostic patterns to your failing GitHub Actions workflow to resolve the localhost certificate trust issue.

Frequently Asked Questions about ci-loopback-oidc-cert-trust

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

FAQPage Schema
Why does my GitHub Actions pipeline fail with AuthenticationException during OIDC token exchange when local tests pass?

You resolve untrusted localhost HTTPS certificate failures in GitHub Actions by implementing environment-specific trust wiring for OpenSSL and Kestrel development certificates to ensure consistent test execution for .NET Aspire environments.

How do I configure OpenSSL trust for Aspire loopback OIDC providers on Linux CI runners?

To configure OpenSSL trust for Aspire loopback OIDC providers on Linux CI runners, apply specific diagnostic recipes that wire environment-specific certificate trust for Kestrel development certificates within your GitHub Actions workflow.

When do I need to implement environment-specific trust wiring for HTTPS development certificates in CI?

When your GitHub Actions workflow executes local auth lanes and encounters untrusted root exceptions during OIDC token exchange against Aspire-backed providers, you need environment-specific trust wiring for HTTPS development certificates in CI.

Does this diagnostic approach distinguish between actual application logic regressions and environment-specific certificate trust issues?

Yes, the diagnostic framework distinguishes between environment-specific certificate trust issues and actual application logic regressions by providing a structured approach to isolate OpenSSL and Kestrel development certificate failures in GitHub Actions.

What is the best way to fix intermittent CI failures for untrusted localhost HTTPS certificates in .NET Aspire environments?

The best way to fix intermittent CI failures for untrusted localhost HTTPS certificates in .NET Aspire environments is to apply structured diagnostic patterns that configure OpenSSL trust specifically for GitHub Actions Linux runners.