Fhi.ClientCredentials.Refit 1.1.1

Fhi.ClientCredentials.Refit

This package contains code to simplify working with Refit and HelseId.

Usage

Include this code in your WebApi startup builder. Don't forget to call UseCorrelationId() after building your application if you are using Correlation Id:

builder.AddClientCredentialsRefitBuilder()
    .AddRefitClient<IMyRefitClient>();

...

app.UseCorrelationId();

The code loads your configuration from IConfiguration using the section "ClientCredentialsConfiguration". If you want to override which section to use you can pass the correct section to AddClientCredentialsKeypairs:

builder.AddClientCredentialsRefitBuilder("CustomClientCredentialsConfiguration")
    .AddRefitClient<IMyRefitClient>();

The default RefitSettings we are using use SystemTextJsonContentSerializer, is case insensitive and use camelCasing. If you want to override the default RefitSettings to use you can pass the settings to AddClientCredentialsKeypairs:

builder.AddClientCredentialsRefitBuilder(new RefitSettings())
    .AddRefitClient<IMyRefitClient>();

Options

This default setup will add a token handler, logging handler, correlationId handler and an header-encoding handler to your Refit Interface. In addition you can add multiple custom delegates if needed.

To add custom delegates use the AddHandler() function:

builder.AddClientCredentialsRefitBuilder()
    .AddHandler<MyOwnLoggingDelegationHandler>();

You can also choose which handlers to use if you prefer not to use all the default handlers:

builder.AddClientCredentialsRefitBuilder(builderOptions: new RefitClientCredentialsBuilderOptions()
    {
        UseAnonymizationLogger = true,
        HtmlEncodeFhiHeaders = true,
        UseCorrelationId = true,
        UseDefaultTokenHandler = true,
    })
    .AddRefitClient<IMyRefitClient>();

Correlation Id

The Correlation Id Handler adds header propagation of the default FHI correlation id header.

builder.AddClientCredentialsRefitBuilder()
    .AddCorrelationId()
    .AddRefitClient<IMyRefitClient>();

A new correlation ID will be given to each request and response that does not contain the header when invoked. Remember to add usage of header propagation to your app startup code. It should be placed before any logging middleware:

app.UseCorrelationId();

Logging

The handler "LoggingDelegationHandler" log all Refit requests with anonymized URLs. The logger requires dependency injection of a Microsoft.Extensions.Logging.ILogger.

The LoggingDelegationHandler will log the following messages. Uri will have all Norwegian National identity numbers replaced with start '***********), and the query parameters removed:

    Requested HTTP {RequestMethod} {Uri} in {Elapsed}ms with response {StatusCode} {Reason} with CorrelationId {CorrelationId}
    Requested HTTP {RequestMethod} {Uri} in {Elapsed}ms with exception {Exception} with CorrelationId {CorrelationId}

WebApi Default Logger issues

The default implementation of HttpClientFactry sets the complete URI in the logging Scope, which might contain sensitive information that we are not able to remove.

F.ex. will your log include this if you are using structured logging (json etc):

Scope: [{ "HTTP GET http://api/person/12345678901/?evenDangerousQueryParams=true"}]

We therefore remove all default loggers created by the WebApi-framework.

If you wish to preserve the default loggers use

builder.AddClientCredentialsRefitBuilder(builderOptions: new RefitClientCredentialsBuilderOptions()
    {
        PreserveDefaultLogger = true,
    })
    .AddRefitClient<IMyRefitClient>();

Header encoding

If HtmlEncodeFhiHeaders is enabled all headers starting with the prefix "fhi-" will be automatically Html-encoded. This is useful when using headers like "fhi-organization-name", which might contain illegal HTTP header characters.

The HTML encoding should only encode characters that are normally illegal in headers. If we did not encode them the requests would fail.

Note that headers are not automatically decoded on the receiving server! You will still have to do your own decoding (using HttpUtility.HtmlDecode or similar), as there are no standard header-encoding rules.

Html-encoding is used over Url-encoding, since more "normal" characters, like spaces, are preserved.