Rstudio Install instruccions, PAM autentication [SOLVED]

[Andy_Wismer (André Wismer)]

@hector

Hello Héctor

I’m not quite sure, but I have a feeling that it could have to do with the SSL Certs used by the NethServer AD.

Even if you have correct LetsEncrypt SSL Certs, the AD uses it’s own, self generated certs, which are not accepted by a lot of Apps.

A solution could be: Copy over the LetsEncrypt Certs over to the NDSC SSL Folder, best done with a software hook on the LetsEncrypt renewal script.

See this post by Elleni, after we had a good discussion and ideas:

[solved] Enable certificate renewal-hook in nethserver

I have placed a script in /etc/letsencrypt/renewal-hooks/post/ as I want the letsencrypt certificate being pushed to my rooter upon renewal. The script works fine, as it is executed when issuing: certbot renew --dry-run thus the certificate appears on my router. Is it possible that this is not the case with normal renewal within nethserver renewal routine? I am asking, as issuing /usr/libexec/nethserver/letsencrypt-certs -f does not make appear the certificate on my router. By the way I found t…

This should help with your AD issue…

My 2 cents
Andy