webauthn implementation

nilsbehlen commented 3 years ago

Feature (closes #1):

Implemented PIWebAuthnSignRequest to be able to recognize when a webauthn token was triggered
A button will be shown in the UI if a SIgnRequest is available
Implemented ValidateCheckWebAuthn to send the SignResponse that is received from the browser to privacyIDEA

Internally:

Fixed namespace names
Put try-catch block around usages of dynmaic to prevent crashes
Refactored the usage of HttpClient to use StringContent instead of FormUrlEncoded so that we can decide what to encode. (encoding the SignResponse breaks it for the server)
SendRequest now properly uses the headers if any are passed

nilsbehlen commented 3 years ago

Please consider my suggestions for naming of multiChallenge->Challenges and otp->interactive.

If not now (maybe we can let it sink in for a while) then maybe later.

I made a new issue for that (#8). Since it is not really related to webauthn i would just merge this PR now

cornelinux commented 3 years ago

Please consider my suggestions for naming of multiChallenge->Challenges and otp->interactive. If not now (maybe we can let it sink in for a while) then maybe later.

I made a new issue for that (#8). Since it is not really related to webauthn i would just merge this PR now

This is a good idea! Thanks.

cornelinux commented 3 years ago

As for me this could be merged. I think @lukasmatusiewicz will also take a look at it?

privacyidea / adfs-provider

webauthn implementation #7