User account management


1

Is there a simple user account management tool?

An table: username, encrypted password, name. And an embeddable form to fill and update the password.

Our potential users aren't tech savvy enough to use OpenId.

There is no database so far and it's much easier for us to keep it this way.

If this is a bad idea, please tell me why.

Thanks!

Alex

Tools

asked May 26 '10 at 22:08
Blank
Alex
32 points
  • Ehmn, which programming language are we talking about, and which kind of software (desktop application, web application, Intranet) ? – Jesper Mortensen 9 years ago
  • It's a web application. .NET, c#. – Alex 9 years ago

1 Answer


1

You could try to ask this question on Stackoverflow.com (with more information); maybe they can think of something better.

Assuming we're talking about a web application, you could use something like RPX (a hosted user authentication service), Facebook Connect, or Microsoft's Live ID.

On .NET something like Dot Net Invoice could be helpful -- but it's way overkill for simple user authentication, and it probably requires a database.

Just about every modern web application framework should make user accounts simple to implement. And for most web frameworks you can find sample applications, from which you can more or less copy'n'paste a working accounts and permissions system. People generally use SQL databases for this kind of stuff, because they are a good solution to this problem.

Personally, I would never outsource user accounts to something like RPX. Users are your company's life and blood, and creating your own user account system is simple. Risking that some users don't understand the login process and abandon the site simply isn't worth it.

If my app was deeply integrated with Facebook, Microsoft Live, or some other large online world, then I would utilize the platforms user authentication to make things easier for the end users. If my app was strongly oriented towards geeks and Internet-sawwy people, then I might use a combination of self-hosted authentication and OpenID, because some of those users prefer OpenID. In all other situations I would use a self-hosted, inhouse developed user management & permissions system, based on email address & password, because that's what most non-technical users know and expect.

answered May 26 '10 at 23:24
Blank
Jesper Mortensen
15,292 points
  • Makes sense. Thanks! – Alex 9 years ago

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Tools