aep-tower 0.2.0

Tower integration for Agent Enrollment Protocol Services.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

# aep-tower

`aep-tower` connects the framework-neutral `aep-service` engine to Tower-compatible HTTP stacks.
It provides a command service for the AEP discovery and lifecycle endpoints and an authentication
layer for protected application resources.

## Install

```toml
[dependencies]
aep-service = "0.2"
aep-tower = "0.2"
```

## Command endpoints

```rust
use std::sync::Arc;

use aep_service::Service;
use aep_tower::CommandService;

# fn example(service: Arc<Service>) -> Result<(), aep_tower::TowerError> {
let commands = CommandService::new(service, 1 << 20)?;
# let _ = commands;
# Ok(())
# }
```

Mount the percent-encoded HTTP paths returned by `CommandService::paths()` without decoding them.
The Service's Inspect document retains the configured `endpoint_base`. The adapter
handles Inspect, Enroll, Status, Grant, and Revoke while enforcing the methods, authentication,
idempotency, body limit, and AEP response media types.

## Protected resources

Apply `AuthenticationLayer` to application resources that require an enrolled Agent. Successful
authentication inserts `AuthenticatedPrincipal` into the request extensions. The configured
origin is used to construct the absolute protected-resource URL bound into JWT client assertions.
Plaintext HTTP is rejected unless explicitly enabled for a loopback origin.

The [`aep-local-lifecycle`](../../examples/aep-local-lifecycle/) example uses `CommandService`
directly. The [`aep-service-axum`](../../examples/aep-service-axum/) example shows the same Tower
boundaries composed through Axum.

The underlying `aep-service` crate remains usable without Tower. See the
[workspace guide](../../README.md) and the
[AEP specifications](https://github.com/aep-foundation/aep-specs).