Tag Info

New answers tagged

0

The complexity of password requirement should be balanced with the contents of your sites. A bank should require a highly complex password (uppercase, lowercase, number, and special characters). However, if the content is trivial, like saved searches and tracking numbers, the password requirement should be relaxed. Minimum length of 6 characters should be ...


1

In a nutshell, you are writing a program that reads information from a protected secure storage facility (so it can call external APIs). The secure storage facility itself has it's own authentication (username/password and possibly multi-factor authentication). And the key is that this authentication to the secure storage facility you want to persist ...


1

I think Oauth providers (twitter, google, fb) will give you what you want: they (arguably store credentials securely ability to authorise applications (not only users) available from API there's probably more features that interest you All you need is to register your application and make some redirections for authentication. It might be not ideal to use ...


3

What you are looking for is Symmetric encryption when the original data is required again. ie Store the important data using Symmetric encryption. Your application then provides access to external applications that can provide a User and password. The calling tools is authenticated against an Asymmetric stored hash. Such as bcrypt for the Hash. You can ...


0

Don't let users choose passwords. Seriously, I've used US government websites where the password-change procedure involved the site generating a random password and displaying it to me. I don't recommend it, because average users and random passwords leads to passwords on Post-It notes under the keyboard, but it solves the problem of using the same ...



Top 50 recent answers are included