Well like I noted it works for me. Yes it's probably the wrong way to do things, but with the lack of AD/LDAP options and authenticating against them, I had to hack what I had. The current ldap auth may work as-is but I needed to get more data back from the ldap query than the stock implementation provides.
Thinkng about it, I could do an additional ldap query once the stock ldap authentication returns.
0
derek-wilson-10759 12 years ago
This might work, I get the feeling though that it's wrongly done. Not trying to discount your work, but it doesn't quite fit the current design.
Is it possible you could create your own 'onaccept' method that will populate the auth.user.* fields with the correct data?
replies (1)