Currently, doing this results in a deployment failure with a UnproxyableResolutionException:

@Produces
@ApplicationScoped
private IdentityConfiguration initFileConfig() {
    return new IdentityConfigurationBuilder()
        .named("default")
        .stores()
        .file()
        .supportAllFeatures()
        .build();
}

The error is

WELD-001435 Normal scoped bean class org.picketlink.idm.config.IdentityConfiguration is not proxyable because it has no no-args constructor

I suppose the IdentityConfiguration is resolved only once in the whole application runtime, but still it would make sense to want to have the configuration bean Application scoped, and not dependent.

The no-args constructor should be added (this should cost nothing).

If this is not desirable or possible for any reason, the documentation should mention in "⁠7.1.3. Providing a Custom Configuration" that when providing the configuration using a producer (and not by IdentityConfigurationEvent handling), the produced bean must be dependent and not normal-scoped.