1 |
Is there a way to make system accounts authentication on mysql? |
2 |
I know theres a way to do that with ldap but I already have one mysql |
3 |
database to authenticate my domain email accounts and also to my |
4 |
website login system. |
5 |
I will be so happy if it could be done. |
6 |
|
7 |
claudinei matos |
8 |
|
9 |
On 5/19/05, Eric Paynter <eric@×××××××××××.com> wrote: |
10 |
> I assume you mean OpenLDAP... |
11 |
> |
12 |
> The key difference is performance. A web application will typically do an |
13 |
> authorization every time the user hits a page. That's a lot of lookups - a |
14 |
> lot of hits to the database. On the other hand, updates to an |
15 |
> authorization database are relatively rare. OpenLDAP, as an |
16 |
> authentication/authorization tool, is tuned for extremely fast lookups. |
17 |
> The whole way the database is indexed and stored on disk is to provide |
18 |
> lightning fast lookups. However, it's quite slow for updates. Mysql is a |
19 |
> general purpose database. It is tuned quite well for both lookups and |
20 |
> updates. It is much faster than OpenLDAP for updates, but can't even come |
21 |
> close for lookups. |
22 |
> |
23 |
> That being said, with today's hardware, unless you are expecting a lot of |
24 |
> traffic, either one will do. Unless under load, mysql will respond in |
25 |
> milliseconds. However, if load is a concern, OpenLDAP might save you on |
26 |
> hardware costs (don't have to buy as many servers), and it will not add |
27 |
> any latency to you web transactions. But mysql is probably easier to |
28 |
> manage, especially if you already know SQL. |
29 |
> |
30 |
> -Eric |
31 |
|
32 |
-- |
33 |
gentoo-server@g.o mailing list |