There should be a better way for using this library in 3rd party integrations than compiling the library with different parameters. Having every library user go through that process every time a new type of national smartcard is about to be released isn't a sensible use of anyone's time.
And I don't believe the following config override is also an option when using SWIG bindings:
The library's user has to create a subclass and override the methods in order to define other values.
For all I know there might be valid reasons for not allowing to override TSL through config files but at the very least please consider publishing alternate artifacts through CI that are targetting test TSL.
There should be a better way for using this library in 3rd party integrations than compiling the library with different parameters. Having every library user go through that process every time a new type of national smartcard is about to be released isn't a sensible use of anyone's time.
And I don't believe the following config override is also an option when using SWIG bindings:
For all I know there might be valid reasons for not allowing to override TSL through config files but at the very least please consider publishing alternate artifacts through CI that are targetting test TSL.