my-auth-api

Create OIDC identity providers and configure RS256 token verification.

83|Updated May 8, 2026
One-click install
npx skills add https://github.com/myapihq/myapi --skill my-auth-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-auth-api
Source: https://github.com/myapihq/myapi/tree/main/skills/my-auth-api
Command: npx skills add https://github.com/myapihq/myapi --skill my-auth-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of building user authentication systems by providing a managed identity layer for applications built on MyAPI, eliminating the need to integrate and maintain separate auth providers.

Core Features & Use Cases

  • Managed OIDC Identity Provider: Create authentication tenants, register application clients, and provide standard OIDC endpoints for app user sign-in.
  • Secure Token-Based Authentication: Enable RS256 token verification through tenant JWKS endpoints with support for hosted login flows and multiple sign-in methods.
  • Use Case: Build a production-ready web application that needs user accounts, Google sign-in, password authentication, or magic links without deploying your own identity infrastructure.

Quick Start

Use the my-auth-api skill to create an authentication tenant and configure user login for my application.

Frequently Asked Questions about my-auth-api

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

FAQPage Schema
How do I add user authentication to my web application without managing my own identity infrastructure?

You can add user authentication without maintaining identity infrastructure by using a managed OIDC identity provider to create authentication tenants, register application clients, and handle user login flows automatically.

Does this managed authentication support RS256 token verification and JWKS endpoints?

Yes, managed authentication supports RS256 token verification and validates security through tenant JWKS endpoints, ensuring secure token-based authentication for your application's end users.

Can I use OAuth flows and Google sign-in with this OIDC identity provider?

You can use OAuth flows and multiple sign-in methods including Google sign-in, password authentication, and magic links by configuring your application clients within the managed OIDC identity provider.

What is the best way to configure a tenant for user login and client registration?

The best way to configure user login is to create an authentication tenant and register OIDC-compatible application clients, which provides standard OIDC endpoints for app user sign-in.

Do I need an OIDC-compatible client to use this managed identity provider?

Yes, you need an OIDC-compatible client because the managed identity provider requires standard OIDC protocols, tenant configuration, and JWKS-based security validation to function correctly.

When should I not use a managed OIDC provider for application end user authentication?

You should not use a managed OIDC provider if your application deployment scenario lacks OIDC-compatible clients or does not require standard OAuth flows, user login, and identity management.