Uses of Package
io.helidon.config.metadata

Packages that use io.helidon.config.metadata
Package
Description
General utilities that use Config.
HTTP APIs and implementations usable by both server and client side of the HTTP story.
Utilities for PKI configuration and loading of certificates and keys.
Configuration metadata to support IDE auto completion and generation of documentation.
Common cross origin configuration and types used by all Helidon flavors.
gRPC client API.
Core classes used by both the reactive gRPC server API and gRPC client API.
Reactive gRPC server API.
Support for Micrometer in Helidon SE.
Integrating with OCI Metrics.
Defines the Helidon metrics API so Helidon metrics-capable components can implement metrics simply and without regard for whether metrics is actually on the runtime path or not or is enabled or not.
Support for OpenAPI in Helidon MP.
Microprofile 1.0 server implementation.
HTTP/2 WebServer.
Metrics endpoint for Níma WebServer.
Open API integration with Níma WebServer.
Support types for REST services.
HTTP/1.1 WebClient.
Níma WebServer module, combining common server API, HTTP API and HTTP/1.1 API to create a server.
WebServer HTTP/1.1 specific APIs.
The Pico API provide these annotation types that are typically used at compile time to assign special meaning to the type.
Pico Tools.
Fault tolerance for Helidon SE reactive implementation.
Health check support for helidon SE.
Common classes for processing content with a specific HttpMediaType.
Metrics endpoint for reactive WebServer.
OpenAPI integration with Helidon Reactive WebServer.
Support types for REST services.
A reactive client for rest calls.
Reactive web server API.
Security
Attribute based access control (ABAC) security provider.
Common classes for provider implementation.
Vault operation backed by configuration.
Integration with Google login button.
Provider that can extract username from a (any) header.
Basic security provider, supporting "basic" and "digest" authentication schemes with role support.
Provider supporting validation of incoming signatures and signing of outbound requests.
Mapper that retrieves roles from IDCS server and maps them to user subject.
Provider that can process incoming JWTs and assert users based on them and can propagate JWTs (or create new ones) for outbound calls.
Integration with Open ID Connect providers.
Open ID Connect (OIDC) classes usable from all OIDC related components.
General utilities for security modules.
Distributed tracing support for Helidon.
Helidon integration with Jaeger tracer.
Open Tracing tracing support that plugs into the TracerBuilder SPI and provides a Tracer implementation.
Brave based Open Tracing implementation for an integration with Zipkin.