Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When using distributed authentication with automatic account creation turned off or admin moderated, the error when you try and login is confusing (unrecognised username or password).
The documentation should be clear (maybe above the select where you choose to not allow user accounts in the admin interface) that to have DA work you need auto creation on.
-Mark
Comment | File | Size | Author |
---|---|---|---|
#4 | jabber.module | 5.68 KB | jsilence |
Comments
Comment #1
Mark Cheverton CreditAttribution: Mark Cheverton commentedOn Mon, 2003-06-09 at 16:48, Ennui wrote:
> The documentation should be clear (maybe above the select where you
> choose to not allow user accounts in the admin interface) that to have
> DA work you need auto creation on.
>
To qualify this outside of the bug system. Personally I'd like to have
the option of account creation off and external auth on, eg I want my
site to run off an LDAP server only which is going to need an external
signup system rather than directing users to the drupal registration.
-Mark
Comment #2
moshe weitzman CreditAttribution: moshe weitzman commentedtoday's patch for user.module in ldap_integration directory makes explicit this requirement as well as implementing Mark's suggestion of 'exclusive external authentication'
assigning this to myself as i am awaiting some feedback before submitting the patch for CVS review
Comment #3
teradome CreditAttribution: teradome commentedThere's no reason that this couldn't work with admin approval on.
Admin approval on would support this process:
- users can create own local system accounts, but must be approved by admin
- users using a Drupal ID skip the approval process: account is still active on RPC'd server so it is considered acceptable
Drupal.module controls the user's choice of accepting Drupal IDs or not, so even if admin approval is on, and the above process isn't implemented, a user trying to login with one shouldn't be blocked, they should be dropped into the approval process with everyone else -- at the least.
Are either of these the process in the CVS version of Drupal?
Comment #4
jsilence CreditAttribution: jsilence commented>> To qualify this outside of the bug system. Personally I'd like to have
>> the option of account creation off and external auth on, eg I want my
Drupal site to run exclusively against a jabber server. Is anybody working on the jabber.module or does anyone know why it is not in 4.4 any more?
I managed to get the 4.3 Version running. The was an issue with a foreach warning using this module. I fixed it (File attached).
I'd like to enhance the module by adding "change password" and "registration" against a jabber server. Specifying a default jabber server and using this one for authentication if no @server is given as a user name would be nice.
Currently I am a bit unsure on how the modules' functions are called. Specially in which order an with which precedence when two modules implement the same function. Can someone enlighten me?
-silence
Comment #5
moshe weitzman CreditAttribution: moshe weitzman commentedComment #6
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedThe jabber module has been discontinued for lack of a maintainer. If you want to be the new maintainer, please apply by sending mail to drupal-devel.