Open GoogleCodeExporter opened 8 years ago
LDAP can already act as an authentication backend. Using SSO usually lets you
sign on once in the morning and then just live with the ticket you've been
granted. In the case of a a password store that is usually not what you want.
Of course maybe the sysadmin should be able to configure this to fit their
unique requirements best, but I have trouble figuring out when it would make
sense.
Original comment by paul.tot...@gmail.com
on 28 Jun 2012 at 7:47
[deleted comment]
Hi Paul,
LDAP is the authentication used for back end. Agreed.
However the objective here would be to use either kerberos authentication or
http post binding with ldap. This works hand in hand with LDAP backend
authentication.
With this in place, there would be no need to keep on typing in the user name
and password, whenever you login to windows, you should be able to access
webpasswordsafe with a click of the mouse.
This would be an advantage to this application.
Original comment by ka...@care.net.sg
on 28 Jun 2012 at 7:53
Original issue reported on code.google.com by
ka...@care.net.sg
on 21 Jun 2012 at 3:20