Instead of always relying on a proof-configuration stored in vc-authn's database, it would be nice to be able to pass a configuration as a query parameter. This would enable applications to use the service without having to have their proof-request pre-approved/loaded in the system - useful for development/sandbox environments as well as self-serve type of consumers.
Nice to have: a configuration setting to turn this feature on/off selectively (when off, only pre-stored proof-configurations selected by id would be accepted.
Note.: this might be problematic for the validation on the client-side of the requested proof, since there would be no guarantee of authenticity/uniqueness of the proof configuration id.
Instead of always relying on a proof-configuration stored in
vc-authn's database, it would be nice to be able to pass a configuration as a query parameter. This would enable applications to use the service without having to have their proof-request pre-approved/loaded in the system - useful for development/sandbox environments as well as self-serve type of consumers.Nice to have: a configuration setting to turn this feature on/off selectively (when off, only pre-stored proof-configurations selected by id would be accepted.
Note.: this might be problematic for the validation on the client-side of the requested proof, since there would be no guarantee of authenticity/uniqueness of the proof configuration id.