kokolegorille
TLS error in dev (with self-signed certificates)
Hello everyone,
I am trying to authenticate users from a Windows 2016 ADFS into my Phoenix application.
It is a bit creepy to configure, and hard to debug.
Currently, I can reach the adfs login page from Phoenix using Samly. It almost work, and yet it does not.
I have setup up https, with self signed certificate for dev.
Those are the logs I get in the console.
[info] TLS :server: In state :hello at tls_handshake.erl:364 generated SERVER ALERT: Fatal - Protocol Version
[info] TLS :server: In state :certify received CLIENT ALERT: Fatal - Certificate Unknown
It works with proper certificates, and it works in prod. But I cannot make it work in dev, with self-signed certificates.
Is there a possibility to communicate with Windows 2016 using tls 1.2? Is there something I miss in the process?
I know it’s very specific, but if anybody has done similar interaction with Windows I’ll be glad to have some hints.
Thanks for taking time
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 3 of 3 Posts
dimitarvp
Maybe the TLS god @voltone can help?
tangui
This might be a problem with Erlang’s TLS implementation rejecting self-signed certificates by default.
See here how to fix it: Allowing TLS connection of clients with self-signed certificates
kokolegorille
Thank You for the response, I am going to see if this solves my problem.
At least the second error is about the client browser sending alert… which has nothing to do with phoenix, nor windows