OptionsValidationException: The 'Instance' option must be provided

[eloekset]

The issue #13311 is resolved and a PR is merged and included in the 3.0.0 release.

I'm trying to build a module for PiranhaCMS based on version 3.1.6 of Microsoft.AspNetCore.Authentication.AzureAD.UI to be used optionally instead of the default Piranha.AspNetCore.Identity module. But when I register the services as explained in the official MS docs, I run into the same issue as #13311.

OptionsValidationException: The 'Instance' option must be provided.

Stacktrace:

Microsoft.Extensions.Options.OptionsFactory<TOptions>.Create(string name)
Microsoft.Extensions.Options.OptionsMonitor<TOptions>+<>c__DisplayClass11_0.<Get>b__0()
System.Lazy<T>.ViaFactory(LazyThreadSafetyMode mode)
System.Lazy<T>.ExecutionAndPublication(LazyHelper executionAndPublication, bool useDefaultConstructor)
System.Lazy<T>.CreateValue()
System.Lazy<T>.get_Value()
Microsoft.Extensions.Options.OptionsCache<TOptions>.GetOrAdd(string name, Func<TOptions> createOptions)
Microsoft.Extensions.Options.OptionsMonitor<TOptions>.Get(string name)
Microsoft.AspNetCore.Authentication.AzureAD.UI.AzureADOpenIdConnectOptionsConfiguration.Configure(string name, OpenIdConnectOptions options)
Microsoft.Extensions.Options.OptionsFactory<TOptions>.Create(string name)
Microsoft.Extensions.Options.OptionsMonitor<TOptions>+<>c__DisplayClass11_0.<Get>b__0()
System.Lazy<T>.ViaFactory(LazyThreadSafetyMode mode)
System.Lazy<T>.ExecutionAndPublication(LazyHelper executionAndPublication, bool useDefaultConstructor)
System.Lazy<T>.CreateValue()
System.Lazy<T>.get_Value()
Microsoft.Extensions.Options.OptionsCache<TOptions>.GetOrAdd(string name, Func<TOptions> createOptions)
Microsoft.Extensions.Options.OptionsMonitor<TOptions>.Get(string name)
Microsoft.AspNetCore.Authentication.AuthenticationHandler<TOptions>.InitializeAsync(AuthenticationScheme scheme, HttpContext context)
Microsoft.AspNetCore.Authentication.AuthenticationHandlerProvider.GetHandlerAsync(HttpContext context, string authenticationScheme)
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
Piranha.AspNetCore.SitemapMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in SitemapMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.StartPageMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in StartPageMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.ArchiveMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in ArchiveMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.PostMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in PostMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.PageMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in PageMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.AliasMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in AliasMiddleware.cs
            await _next.Invoke(context);
Piranha.AspNetCore.ApplicationMiddleware.Invoke(HttpContext context, IApi api, IApplicationService service) in ApplicationMiddleware.cs
            await _next.Invoke(context);
Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

I created this PR as a reference: eloekset/piranha.core#9

And the appsettings.json definitely has the Instance property set:

I use the MvcWeb test application included in the Piranha solution:

[tidyui]

@eloekset Are you sure you’re using the latest version of the docs? Given that the example contains the following line:

.SetCompatibilityVersion(CompatibilityVersion.Version_2_1);

Is it really compatible with asp.net core 3.1? I know there were a couple of changes affecting startup configuration between 2.x and 3.x, especially regarding the order of how security components should be registered.

[eloekset]

To confirm that it works out of the box with a ASP.NET Core 3.1 application, I used the File -> New Project template that configures authentication with Work or School Accounts (although I'm neither at work nor school - I just want to use Azure AD).

I think I'll have to look at how to disable the default Piranha.AspNetCore.Identity module, because there's probably a conflict as mentioned in #13311 or something similar. However it's very difficult to guess what's going on inside these libraries and resolve these kind of issues.

[tidyui]

I think in your case you can just remove the a Piranha Identity packages all together. You will loose the management UI, but you’ll manage your users from within Azure AD anyway. Also you’ll need to register a service for the ISecurity interface so Piranha knows how to authenticate users when logging into the manager.

[eloekset]

OMG, I overlooked a minor detail with major impact. The options object didn't get bound to the configuration. Commit that fixes the issue: eloekset/piranha.core@3d8deeb

And a picture in case I change the branch so the commit link becomes invalid:

There's obviously more work to be done to this module, but we'll continue that discussion over at the Piranha project, since it's out of scope of the Azure AD authentication library.