All Classes and Interfaces
Class
Description
Resulting conditions for letting the user access.
Initialize everything before starting spring container, especially libraries using statics.
Holds a SAMLArtifactMap needed to store SAML objects for the SAML artifact binding
Registry for attribute names populated through AttributeInitializer implementations and from configuration.
Unmarshaller for opensaml4 compatibility that can handle this nesting:
application.yml config helper methods.
This AttributeInitializer runs first, so it will take precedence in case of conflicts.
Standard attribute names and additional ones used by XTB.
SAML encoder that allows custom parameters for a custom template.
An implementation of a ProxyDataFactory based on the CustomProxySelector.
Error code for the UI.
Static error marker.
HTTP utility functions.
Util class for Jose JWK.
Mutable version of AttributeName to allow updating of enum values based on config.
SAML encoder that does not flush the response stream.
This class is used to do manual operation tracing (OP-tracing).
Combination of regular expression, an optional name of an item to match against that regex, and a value to use if matching.
Implemented by classes that provide an application wide request context.
Factory for getting hold of the currently valid request context.
Use this exception when we have failures because of input data from network, and we blame the client.
Skinny SAML messages handling requires rewriting the opensaml output DOM.
Pointcut to allow @Traced annotation on services doing client calls to external services the trustbroker depends on.
Use this exception when we have failures because of configuration, infrastructure or internal code problems.
Annotate injected classes on class or public method level to get tracing.
EXPERIMENTAL SAML2 GET/POST encoder allowing to send OpenTelemetry traceparent header using XMLHttpRequest.
This class adopts the OpenTelemetry effort providing these features:
MDC traceId to tag every log line with the OpenTelemetry compatible traceId.spanId where spanId is our own root
OpTrace logs are tagged with trID=traceId.spanId for request based tracing
The related W3C specification lists these propagations:
traceparent is set by XTB if not received from client, we derive traceId from x-request-id if it's compliant.
tracestate is not (yet) supported
Note that the ID displayed in error screen are either based on current requests or the related login conversation
depending on the processing phase within XTB.
renderTemplate copied from HTTPPostEncoder and adapted.
Log-able web input (where we do not expected any StringUtil.clean modified data) and other helpers.