How can you 'configure' OpenIdConnectOptions CallbackPath?

[MarkPflug]

I'm trying to set the OpenIdConnectOptions.CallbackPath through appsettings.json configuration, but it throws an exception when I attempt to access the IOptions Value property.

System.InvalidOperationException occurred
  HResult=0x80131509
  Message=Failed to convert '/OpenIdCallback' to type 'Microsoft.AspNetCore.Http.PathString'.
  Source=Microsoft.Extensions.Configuration.Binder
  StackTrace:
   at Microsoft.Extensions.Configuration.ConfigurationBinder.ConvertValue(Type type, String value)
   at Microsoft.Extensions.Configuration.ConfigurationBinder.BindInstance(Type type, Object instance, IConfiguration config)
  ...
Inner Exception 1:
NotSupportedException: TypeConverter cannot convert from System.String.

I can set this value in code, because there is an implicit conversion from string to PathString. Is there a way to set it through configuration?

[HaoK]

Yeah there's no support for PathStrings in the binder yet, I'll file an issue for this in Configuration

[Tratcher]

What's dynamic about your CallbackPath such that you need to set it from config?

[MarkPflug]

I can probably get away with the default, for now. However, I would expect that all properties on "Options" types of objects to be able to be initialized via configuration. Perhaps that is a mistaken assumption on my part.

The ultimate goal, is to be able to add new OpenId auth providers purely through configuration. If I have more than one OpenId provider, can they use the same callback endpoint? If not, I'll need to be able to configure it for each provider.

[Tratcher]

OIDC providers should use unique callback paths.

[MarkPflug]

Right, that's what I was expecting. So, to accomplish what I'm trying to do I'll need to be able to configure the CallbackPath via configuration, which is not currently possible.
I can work around this, by creating a "configurable" OpenIdConnectOptionsEx class, that simply uses string instead of PathString, and map it at runtime back to an OpenIdConnectOptions instance, but I was hoping to avoid that.
Thanks for the quick responses.

[MarkPflug]

Nevermind. I found a better solution; register a custom TypeConverter for PathString:

TypeDescriptor.AddAttributes(typeof(PathString), new TypeConverterAttribute(typeof(PathStringConverter)));

public class PathStringConverter : TypeConverter
{
    public override object ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, object value)
    {
        return new PathString((string) value);
    }
}

This appears to work, though it feels like this should be provided by the assembly that PathString belongs to. At least if someone else runs into this issue they can use this as a solution.

[MarkPflug]

I created an issue over in HttpAbstractions to track this, I'm assuming that will be the "fix". If you guys deem this worth fixing.

[HaoK]

Yeah PathString should be fixed since its basically a string+ primitive, binding should work for it

[Eilon]

@HaoK - can you close and link to the PR?