The solution I developed for the client was based on the premises that if you were logged onto the network (it was an intranet) you wre good to go with farcry. So it picked up CGI.remote_user and passed that to the ldap functions.

The login.cfm basically just set up dmProfile and dmSec. I still had login.cfm for the client login (eg use the farcry account) for cases where there was a problem with Active Directory.

Using LDAP authentication would be a matter of extending - phhhss, been awhile since I have been here. let me know if you need particular info and I will have a dig through the project.

On 12/6/05, Shib71 <[EMAIL PROTECTED]> wrote:
G'day Andrew

According to the archives, you've spent a bit of time fixing the long groups problem with AD. What exactly was involved?

Blair

On 12/6/05, Shib71 < [EMAIL PROTECTED]> wrote:
That's fine if I want to completely ignore the authentication framework already in place, but I want to COMBINE FarCry's user level permission management with AD authentication, not start again from scratch.

Blair


On 12/6/05, Andrew Mercer < [EMAIL PROTECTED]> wrote:
Yes it is. The farcry core login process looks for an existance of login.cfm in customadmin\login of your application directory.



Reply via email to