Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions example/04-nlap-integration/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# Example 4: NLAP Proxy Integration

> **Note:** This example is a **template** for future implementation of NLAP Proxy Authentication integration with Python MicroESB.

## Overview

This example will demonstrate how to integrate Python MicroESB with the **NLAP (Network Layer Authentication Protocol) Proxy** for secure, authenticated service communication.

## NLAP Proxy

The NLAP Proxy is an advanced authentication and security layer for NLAP protocol communication. For more information, see the NLAP (Next Level Application Protocol) project:
Comment on lines +7 to +11
Copy link

Copilot AI Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The NLAP acronym is defined inconsistently. On line 7, it's expanded as "Network Layer Authentication Protocol" but on line 11, it's expanded as "Next Level Application Protocol". Please ensure the acronym expansion is consistent throughout the documentation. Based on the GitHub repository link provided, it appears the correct expansion is "Next Level Application Protocol".

Copilot uses AI. Check for mistakes.

**External Link:** [https://github.com/WEBcodeX1/http-1.2](https://github.com/WEBcodeX1/http-1.2)

### Key Security Features

The NLAP Proxy implementation enforces the following security requirements:

1. **Encrypted Communication Only**
- The proxy will **not** communicate unencrypted
- All traffic must use encrypted channels

2. **Restricted Communication Scope**
- The proxy will **not** allow global communication
- Communication is restricted to authorized endpoints only

3. **X.509 Certificate-Based Authentication**
- The proxy will **only** allow communication by X.509 client certificates
Copy link

Copilot AI Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "allow communication by X.509 client certificates" uses an incorrect preposition. It should be "allow communication with X.509 client certificates" or "allow communication using X.509 client certificates" to be grammatically correct.

Suggested change
- The proxy will **only** allow communication by X.509 client certificates
- The proxy will **only** allow communication with X.509 client certificates

Copilot uses AI. Check for mistakes.
- Client authentication is mandatory for all connections

## Future Implementation

This example will cover:

- Setting up NLAP Proxy for MicroESB services
- Configuring X.509 client certificate authentication
- Integrating encrypted communication channels
- Service routing through the NLAP Proxy
- Load balancing and service scaling with NLAP authentication

## Prerequisites

- Python 3.8 or later
- NLAP Proxy (see external link above)
- X.509 client and server certificates
- Python MicroESB package

## Additional Information

For more detailed documentation on Python MicroESB, see: [https://pythondocs.webcodex.de/micro-esb/examples.html](https://pythondocs.webcodex.de/micro-esb/examples.html)
Loading