Allow LDAP integration

[weijian19391]

Is there anyway to allow LDAP integration for the current login package?

[splendido]

No, I'm sorry that's not possible at the moment. :(
...but I'm interested to make this possible for version 2.0: so feel free to make proposal about what we could write for a useraccounts:ldap package.

[kayrules]

+1 for ldap feature.

[chazsolo]

Is there any progress on this? I'd absolutely love to keep using this package for account management but I'm on a project that will require both LDAP and client account creation.

[chazsolo]

@splendido I've been messing around with a local clone of the useraccounts:core package in an attempt to get an LDAP package I wrote (not published yet, still has a lot of work to do, but it's based off the tdamsma ldap package). It's meant to work seamlessly within the same form. Essentially it would look something like this:

In at_pwd_form.js

if (state === "signIn") {
    let pwdOk = !!password;
    let userOk = true;
    let loginSelector;

    // ...

    // Here we would check if a customLoginMethod has been assigned
    // if so, call it passing in the same parameters and calling the same callback
    if ( _.isFunction(AccountsTemplates.customLoginMethod) ) {
        return AccountsTemplates.customPasswordLoginMethod(loginSelector, password, error => {
            AccountsTemplates.submitCallback(error, state);
        });
    } else {
        // this was the original call
        return Meteor.loginWithPassword(loginSelector, password, error => {
            AccountsTemplates.submitCallback(error, state);
        });
    }
}

Calling a separate function would allow a user to set up their custom login logic client-side, probably where they set up the rest of the AccountsTemplates config.

if ( Meteor.isClient ) {
    AccountsTemplates.customPasswordLoginMethod = ( loginSelector, password, callback ) => {
        return Meteor.loginWithLDAP(loginSelector, password, function( error ) {
            if ( error && error.reason == 'Invalid username' ) {
                console.log('Could not find user in LDAP, checking local accounts...');
                return Meteor.loginWithPassword(loginSelector, password, error => {
                    callback(error);
                });
            } else {
                callback(error);
            }
        });
    }
}

In my example, if I don't find a user because of an invalid username, I continue on a check to a local account (as the app I'm building requires both LDAP users and non-ldap users together).

Do you have any thoughts on this? I'm sure I haven't thought of all the cases where this would apply, but I'd be happy to help with advising or implementation. I think you would agree that perhaps useraccounts shouldn't care what the custom login methods are, but it should be able to call them if the user wants them to.

Let me know what you think!