Fen.Service 4.3.1

Standardized Service conventions, from the opinions of the Fulfiller Enablement team.

Install-Package Fen.Service -Version 4.3.1

dotnet add package Fen.Service --version 4.3.1

<PackageReference Include="Fen.Service" Version="4.3.1" />

paket add Fen.Service --version 4.3.1

Release Notes

➟ Release 4.3.1
⁃ The lowest level of authentication support has been raised from "implicit" to "accessCode".
⁃ Endpoints allowing anonymous access are no longer erroneously reported as requiring authentication in Swagger definitions.

➟ Release 4.3.0
⁃ Validation failures now respond correctly as problem responses.
⁃ A model binder for partially unescaped URIs (from route parameters) has been added.
⁃ Debug symbols are now pushed to NuGet for client retrieval.
⁃ A near-trivial amount of overhead has been removed from application startup.

➟ Release 4.2.3
⁃ Configuration and use of X-Ray Middleware has been made more idiomatic to ASP.NET Core.
⁃ Secrets Manager support now comes from an external library, Tiger.Secrets.
⁃ The enhanced Swagger document middleware should interfere less with replacement of the response stream.

➟ Release 4.2.2
⁃ Display of lower-cased paths in Swagger definitions has been improved.
⁃ AWS X-Ray dependencies have been upgraded to a stable release.
⁃ An alternative key delimiter for Secrets Manager secrets has been introduced.
 ⁃ If a secret needs to be referenced in a CloudFormation dynamic reference, a double-underscore (__, or "dunder") may be used in lieu of colon (:).
⁃ Compatibility with Microsoft.AspNetCore.App has been updated as far as 2.1.6.

➟ Release 4.2.1
⁃ The local development extension point is configured to apply authorization by default.

➟ Release 4.2.0
⁃ Project compatibility has been significantly widened.
⁃ The local development extension point is configured to use standard JWT Bearer authentication.

➟ Release 4.1.2
⁃ A bug related to a missing Startup is fixed.

➟ Release 4.1.1
⁃ The Fen.Authorization library is fully opt-in, and none of its functionality is a dependency to this project.
⁃ AWS X-Ray tracing is integrated into the conventions.
⁃ AWS Secrets Manager has been added as an optional configuration source.

➟ Release 4.0.1
⁃ Healthcheck discoverability has been restored.
⁃ The content type "text/plain" has been un-restored.

➟ Release 4.0.0
⁃ In preparation for hosting on AWS Lambda, a large number of changes have been made to the project.
 ⁃ A customized Lambda entry point has been added.
 ⁃ A local development extension point has been added.
 ⁃ Authentication has been removed in favor of a Lambda Authorizer.
 ⁃ Default CORS rules have been adjusted.
 ⁃ The portions of Auth0 configuration used for generating authentication response headers have been removed.
   ⁃ The remaining properties have been moved into Swashbuckle configuration.
   ⁃ The rules for what an authenticated endpoint is have been altered. (Lacks an `AllowAnonymousAttribute`.)
⁃ The new COAM Conventions are now available by default. (Don't use COAM? No problem. There's no longer a runtime cost.)
⁃ `MinimumAttribute` and `MaximumAttribute` are now exposed to Swagger definition builders.
⁃ ASP.NET Core 2.1 conventions have been applied.

Dependencies

• .NETStandard 2.0

  • Amazon.Lambda.AspNetCoreServer (>= 4.1.0)
  • AWSSDK.Extensions.NETCore.Setup (>= 3.3.100.1)
  • AWSXRayRecorder.Handlers.AspNetCore (>= 2.5.2)
  • AWSXRayRecorder.Handlers.AwsSdk (>= 2.6.2)
  • Microsoft.AspNetCore.Authentication.JwtBearer (>= 2.1.2)
  • Microsoft.AspNetCore.HostFiltering (>= 2.1.1)
  • Microsoft.AspNetCore.Mvc (>= 2.1.3)
  • Microsoft.AspNetCore.Server.Kestrel (>= 2.1.3)
  • Tiger.Healthcheck (>= 6.0.3)
  • Tiger.Secrets (>= 1.1.0)

Used By

Version History