judo-runtime:custom-auth

Implement custom authentication and authorization providers in the JUDO runtime framework.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill judo-runtime-custom-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judo-runtime:custom-auth
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/judo-runtime-core-security/src/main/resources/claude/plugins/judo-security/skills/custom-auth
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill judo-runtime-custom-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide for developers to integrate custom authentication and authorization mechanisms into JUDO applications, moving beyond default Keycloak integration.

Core Features & Use Cases

  • Custom Identity Providers: Integrate with any OAuth2/OIDC compliant identity provider.
  • Flexible Realm Management: Implement custom logic for mapping requests to application realms.
  • Diverse User Stores: Connect to LDAP, databases, or other custom user directories.
  • Advanced Security Policies: Define custom password policies and MFA flows.
  • Use Case: A company needs to integrate its proprietary SSO solution with JUDO applications, requiring custom handling of user authentication and session management.

Quick Start

Implement a custom OpenIdConfigurationProvider by extending the provided Java interface and registering it with Guice or Spring.

Frequently Asked Questions about judo-runtime:custom-auth

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

FAQPage Schema
How do I implement custom authentication in JUDO beyond the default Keycloak integration?

Custom authentication in JUDO is implemented by extending Java interfaces such as OpenIdConfigurationProvider and registering them via Guice or Spring to support non-Keycloak identity providers.

What is a custom realm extractor and when do I need one for authorization?

A custom RealmExtractor maps incoming requests to application realms. You need one when default routing cannot accurately assign requests to the required security realms.

Can I connect JUDO security to an LDAP directory or external user management system?

Yes, JUDO connects to LDAP or custom user directories by implementing the UserManager extension point, enabling diverse user stores for authentication and authorization.

Does JUDO runtime support custom password policies and multi-factor authentication flows?

Yes, JUDO runtime supports custom password policies and MFA flows through dedicated extension points, allowing you to define advanced security policies and specialized token validation.

What is the best way to integrate a proprietary SSO solution with JUDO applications?

The best way to integrate a proprietary SSO solution is to implement custom OpenIdConfigurationProvider and CXF interceptors, handling custom user authentication and session management within JUDO.