We have found the solution. The problem was really with the proxy. A proxy was configured system-wide, but the IIS ignored it and sent the request directly to Microsoft. The response then contained the certificate of the honeypot server and not that of Microsoft, resulting in the RemoteCertificateNameMismatch.
Unfortunately, it was not enough to define the proxy in IIS web.config. We had to create a wpad.dat file (for Web Proxy Auto-Discovery). Then the IIS selected the correct route.
Would be nice if you could refund me the question.
The problem still exists in ABP 7.4.2 and LeptonX 2.4.3
In my case and I think I also speak for @DEKUKDEV it is like this:
Please let us know if you were at least able to reproduce the problem. At least 6 people are waiting for a solution, the problem was reported 2 months ago and it doesn't seem like you are doing anything about it (and otherwise you could at least keep us up to date and communicate a bit more about it).
and we'll release new patch versions for LeptonX for 2.4
I think you didn't mean 2.4, but 2.5?
I have now installed 2.4.2 and can confirm that the points you mentioned have been fixed. The others are still open.
Exception message and full stack trace:
System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
Details:
We use Microsoft Azure as an external login provider. On my development system, everything works fine with the Microsoft login (with another Microsoft Entra ID instance).
When I wanted to install this on our customer's test system and tested the connection to their Entra ID, the authentication could be performed, but the above error occurred during the callback.
The customer, a large company with various security systems, then looked in the firewall and noticed that the callback from Microsoft had landed in their honeypot. He thinks that the reason is probably that the request from our application did not go through the proxy (although this is configured system-wide on the server).
Could this have something to do with the proxy and can I set it explicitly in the application? Or does it have to do with something completely different?
Thank you for your answer. In which version are these bugfixes delivered?
Thanks for the update.
I assume points 1 and 2 are also done? In which update will this be included?
Will the question be refunded?
The ticket should only be closed when it is done...
Hi enisn, can you update the documentation accordingly? Then I will close this ticket.
Hi enisn,
thank you for the feedback. Perfect. It is difficult to reproduce as it does not always occur. Now I have clicked around a bit in the profile menu and now it is displayed correctly...
Can you also fix it so that when you select German it says DE-DE and not just DE? You have already changed this in the submenu. Now all that's missing is the customized display at the top.
Hi, We've just fixed it and it'll be included in the next release
Hi,
Could you please confirm what Release number that would be? because we've just tested Release 7.4.0 and the bug is still present!
Were you referring to the major version number which would make it the upcoming 8.0?
Thanks.
I would also like to have an answer soon... in 7.4.0 it really still does not work. And for us it's getting urgent, because the final release is coming soon... Please try at least to give an answer!
