Client Certificate Authentication (suggested feature)
See original GitHub issueIt would be nice if your app could support Client Certificate Authentication
feature…
Right now with an xmpp server that enforce CCA, it does not work (because its not implemented) and output the current this error message: Encounter problem during XMPP Connection: javax.net.ssl.SSLHandshakeException: Handshake failed
Thanks
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Client Authentication Certificate 101: How to Simplify Access ...
Certificate-based authentication allows users to log in to various systems without typing in a traditional username and password. Instead, the ...
Read more >7 Best Practices for Certificate-Based Authentication - Teleport
Certificate-Based Authentication Best Practices · Forged certificates exploiting weak hashing algorithms · Reuse of stolen certificates ...
Read more >Client Certificate Mapping Authentication ... - Microsoft Learn
Specifies whether Client Certificate Mapping authentication using Active Directory is enabled. For this setting to take effect, you must set ...
Read more >X.509 Client Certificate Authentication Schemes - TechDocs
Certificate authentication uses SSL communication and can be combined with basic authentication to provide an even higher level of access security.
Read more >Authentication using HTTPS client certificates - Medium
In this post, we implement a simple Node. js example which uses client certificates to authenticate the user.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My test server is based on ejabberd community edition. From online info, it seems that client TLS authentication is not being offered on this edition. I am also unable to find any document on the setup, hence unable to perform the full client to server testing.
i saw that, great first base… currently my production server is on a lan… i did not had the time to setup a wan testing vm, i’ll close this issue and reopen it later on, when i’ll be working on this… probably with a PR directly as i am maintaining https://github.com/Intika-Android-Apps/Libre-Messenger and willing either to switch to atalk or implement call/video to that “fork”…
But any way the config is a simple minimalist one, it’s just prosody (how-to) with client certificate enabled with the following config (
prosody.cfg.lua
):The client certificate
ca.crt
had been generated as this guide explainOther config may be used with client ca as authentication system instead of password (this should not impact the implementation)