Open triballo opened 3 years ago
Well, I might be too late for you, but I freaked out too on this issue some months ago. To be more clear: You have to provide a Basic Authentication Header with base64 encoded credentials (username:password). Then you will see the login mask where you are able to just click on login with empty crednetials to login with SSO. My thought was, that I get redirected to the main page with SSO but learned that I have to click on login to get logged in with SSO.
I am not 100% clear on your answer, SSO is still a bag of worms to me!
Do you do that with mod_rewrite -
RequestHeader set Authorization "Basic <base64-encoded login+password>"
in which case where does the user/pass come from?
Or with mod_ntlm which seems to offer
NTLMOfferBasic
NTLMBasicPreferred
Do you possibly have an example apache config?
Sorry if I am asking dumb questions!
unfortunately I have to say no. I tried to let authelia be a SSO Provider which is not possible. My answer refered to manual adding the Header via a Plugin to try out how it works. I can not give you any apache configs either as I use nginx reverse proxy with the sysPass docker container behind.
Well, I might be too late for you, but I freaked out too on this issue some months ago. To be more clear: You have to provide a Basic Authentication Header with base64 encoded credentials (username:password). Then you will see the login mask where you are able to just click on login with empty crednetials to login with SSO. My thought was, that I get redirected to the main page with SSO but learned that I have to click on login to get logged in with SSO.
Unfortunately it does not work, clicking on the login button returns the "Login error" error, analyzing the syspass logs I detect the following messages:
`[2022-01-31 08:46:07] syspass.EXCEPTION: logger {"message":"Errore nel localizzare l'utente in LDAP
[2022-01-31 08:46:07] syspass.EXCEPTION: logger {"message":"Login errato`
sysPass v 3.1
Hello everybody, I am an avid supporter of this wonderful project that I have been using for several years. I have always used login with LDAP but have never been able to configure the SSO function correctly. On the net I searched everywhere but I never found a specific guide that was helpful for a correct configuration. Although I have enabled SSO everywhere in the graphical interface of the portal, every time I try to log in to the home, it offers me the username and password fields and I can only access with AD credentials via LDAP and not via SSO. Is anyone able to give me some advice on how to do some debugging to understand where am I wrong?