Support dynamic "origins" for this library for testing

[witwaycorp]

All,

I have a WebAuthn server using this library and was hoping to modify it so that I can support any sub-domain for the main website for some test scenarios I am working on. Example, the app is deployed to auth.example.com. I however would like to support any sub-domain of example.com like dev.example.com, prod.example.com, etc.

many thanks!

[abergs]

Not sure I follow - you can initiate a new instance of the library with the appropriate configuration for your origin.

[jackaboy7981]

Hey is there a option to set the origin configuration of fido2 to allow all subdomains of a particular domain?

becuse i have a scenario where i will be supporting new subdomains while the project is running so need to add the origins dynamically or set the origin such that it accepts all subdomains

if there is no option available currently , is there any work around for this?

[abergs]

@jackaboy7981 The suggested workaround is to instantiate a Fido2-class with configuration through code, there you can perform any type of dynamic/multi-origin support, pseudo code example:

var origin = new Uri(incomingRequest.Request.Host); // use domain from the incoming request based on headers etc.
builder.Services.AddFido2(options =>
{
    options.ServerDomain = origin.Host;
    options.ServerName = "FIDO2 Server";
    options.Origins = new HashSet<string> { origin.AbsoluteUri };
    options.TimestampDriftTolerance = 1000;
});

[jackaboy7981]

This code should be part of startup right ?
If not, won't this cause service re-registration issues ?

In my use case i will be handling n-number of subdomains and the request should only be accepted from my subdomains.

[abergs]

Not using DI - or using DI with a "scoped" factory like above would match your requirements.

[Regenhardt]

For usage with DI, you can inject something like this FidoFactory and use your own URL-matching logic to decide which hosts you want to allow. Example usage in this UserController.