Idea ID: 2785912

Windows Native SSO for both Desktop and Web Client

Status : Waiting for Votes
Waiting for Votes
See status update history
over 1 year ago
I know about Keyshield/NAM but would like to notice that both are another products (and Keyshield is a 3rd Party) and adds cost into the Project.
Why there is no Windows Native solution at the moment? With Desktop that will be pretty easy as we have all credentials in place after successful Windows authentication&authorization.
With Web I'm in doubts as I have no too much knowledge about Web... but I heard there are a lot of ready-to-use recipes for Web SSO.
That'll be great if we will have SSO in Filr, this will minimize the amount of request for problem related with login, security etc. About Security: right now we're in trouble with Filr and AD Security Policy, if there is a setting on AD side which limits unsuccessful attempts and this limit lower than 6 attempts (6 attempt is hardly-coded in Filr AFAIK) - it leads to account lock on AD side. This creates a lot of pain in the ass for administrators as in big infrastructure it may lead to mass-locking in case if somebody just try to try accounts one by one (this is a real story told me by customer). SSO will eliminate this problem as there will be no Login Window at all.
  • I would like to add that in my experience users will forget about the Filr client when they change their password. We had clients trying for weeks to log in with outdated password information. This leads to intruder lockout, of course, and people complaining at the help desk that they can't use our services any more. A built in SSO solution for the clients will solve this.
  • This would be awesome for both the Windows and Mac desktop client.