mwarning / trigger

Android app to lock/unlock/ring doors. Supports generic HTTPS/SSH/Bluetooth/MQTT and Nuki Smartlock.
GNU General Public License v3.0
133 stars 22 forks source link

HTTPS Client Certificates for authentication #68

Closed cuechan closed 2 years ago

cuechan commented 2 years ago

Hi, we are using Client TLS Certificates for authentication for doorlocks at our hackspace . Unfortunately i was not able to import my certificate into the app. While importing the certificate it shows Done, Read primary:key but when opening the door it fails with 400 No required SSL certificate was sent.

How can i use a TLS Client certificate for authentification?

mwarning commented 2 years ago

The easiest would be to initally fetch the certifiacte from the door. Under "Manage TLS Certificate" you can add a "Certificate URL" (e.g. "https://our-door.net"). This way you can import the certifcate. Then, if you want, you can then export it with the export button.

mwarning commented 2 years ago

Maybe there is a bug that is triggered with your approach, of course. Feel free to send me testing certificates so I can try to recreate the problem on my side. Or instructions.

mwarning commented 2 years ago

More code for TLS support was added. But it was not tested yet. Let's hope that it will this issue.

mwarning commented 2 years ago

So far Trigger did not support client certificates. Now it does, but so far it is not released and untested.

mwarning commented 2 years ago

Closing this ticket. Please open a new ticket if the feature is broken. Thank you.