In my component I publish a UI component that uses an API controller to handle updating of application resources generically. There is a base .NET library that provides core localization services and an ASP.NET Core specific library that provides features specifically for ASP.NET.
The issue is how to allow the API Controller - which lives inside of the generic component and is not touched by the application directly - to be secured easily.
I ended with the following code:
services.AddWestwindGlobalization(opt =>
{