| 662 | | at the beginning of this document. For now, the best way to deal with this is to |
|---|
| 663 | | create a Django User object for each user that exists for your backend (i.e. |
|---|
| 664 | | in your ldap directory, your external sql database, etc.) You can either |
|---|
| | 662 | at the beginning of this document. For now, the best way to deal with this is |
|---|
| | 663 | to create a Django User object for each user that exists for your backend |
|---|
| | 664 | (i.e. in your ldap directory, your external sql database, etc.) You can either |
|---|
| 666 | | it the first time a user logs in. `django.contrib.auth.backends.SettingsBackend`_ |
|---|
| 667 | | is an example of the latter approach. Note that you don't have to save a user's |
|---|
| 668 | | password in the Django User object. Your backend can still check the password |
|---|
| 669 | | against an external source, and return a Django User object. |
|---|
| | 666 | it the first time a user logs in. |
|---|
| | 667 | `django.contrib.auth.backends.SettingsBackend`_ is an example of the latter |
|---|
| | 668 | approach. Note that you don't have to save a user's password in the Django |
|---|
| | 669 | User object. Your backend can still check the password against an external |
|---|
| | 670 | source, and return a Django User object. |
|---|