Basic AD & CFLDAP question

Ask a Question related to Coldfusion - Advanced Techniques, Design and Development.

  1. #1

    Default Basic AD & CFLDAP question

    I need to authenticate AD users in my CF app. All of the articles I've read
    about this assume the username and password combo are supplied (ie:
    username='#form.username#' password='#form.password#') to the CFLDAP tag in
    some fashion. My question is, how can I retrieve the username and password of
    an AD user? Is this is a CGI variable? TIA

    Balance Guest

  2. Similar Questions and Discussions

    1. A Very Basic Question
      Yikes! I read a lot of the online discussion and went through all the help documents, but I couldn't find an answer to this very basic question. ...
    2. CFLDAP Question
      I am trying to pull back all users in Active Directory that do not contain a $ sign. I can return ALL users that have a dollar sign by the...
    3. ASP.NET and SSL basic question.
      Hi, Apologies if this question is a bit basic, but I can't seem to find any documentation anywhere. I have an asp.net site running on Windows...
    4. Very basic ASP.NET question
      I've got some Java experience but no JSP or ASP and am trying to get to grips with ASP.NET. I'd appreciate some help on a simple question. I...
    5. Basic question b/w ASP & ASP .NET
      I would like to know what is the basic difference between ASP and ASP .NET VB AND VB .NET ADO and ADO .NET look forward to your responses
  3. #2

    Default Re: Basic AD & CFLDAP question

    This is easiest on IIS. Using windows authentication will produce two cgi
    variables for you: cgi.auth_user and cgi.auth_password. Using windows auth. on
    IIS with IE will produce a seamless experience for you users. No prompts for
    passwords with that solution. If you are not using windows authentication or
    not using IIS, then you will have to pass the variables through the browser in
    a form. If you are not using IE, and are using IIS, you will be presented with
    a popup asking for u/p.

    When you are authenticating to AD via CFLDAP, the username will be in the
    format [email]username@full.domainname.what[/email]ever as you have it set in AD. See the
    example below:


    our AD domain is acs01.danddaviation.com

    <cfldap action="QUERY"
    name="users"
    attributes="givenname, sn, department, mail"
    start="cn=users,dc=acs01,dc=danddaviation,dc=com"
    server="192.168.0.10"
    port="389"
    filter="(search criteria here)"
    username="user@acs01.danddaviation.com"
    password="mypasswordgoeshere"
    sort="sn" />

    ajpowellatl Guest

  4. #3

    Default Re: Basic AD & CFLDAP question

    Thanks a lot for your reply.

    Shouldn't the username value in your CFLDAP call look like this, though:

    username='#cgi.auth_user#'
    password='#cgi.auth_password#'

    Thanks again
    Balance Guest

  5. #4

    Default Re: Basic AD & CFLDAP question

    Folks, if basic authentication is turned off, AUTH_PASSWORD is not populated
    (with good reason). If you need to authenticate to AD, why don't you administer
    security through the resource itself, i.e. restrict access with AD groups?

    philh Guest

  6. #5

    Default Re: Basic AD & CFLDAP question

    OK. So, again, how can I check the AD username and password of a specific user
    account with CF? We need to integrate our app in a 'single sign-on' environment
    where authentication is handled with AD (but authorization would be handled in
    our CF app).

    Balance Guest

  7. #6

    Default Re: Basic AD & CFLDAP question

    If you want the single sign on, then you will have to turn the basic
    authentication on in the IIS settings. Otherwise, there is no real way to do
    it. There is a required interaction between the browser and server.

    ajpowellatl Guest

  8. #7

    Default Re: Basic AD & CFLDAP question

    OK, before my diatribe, I assume the application, the Web and data servers, and
    the DC are in the same domain/forest/group of trusted domains. I fail to see
    the distinction between authentication to AD and authorization to your app. An
    account that successfully signs in to a domain is unique. The user can't access
    the network until authenticated. Once authenticated, the account can enjoy
    access to all of the resources to which they are authorized through membership
    in AD groups. The only thing you need to know is who they are, not what their
    password is. AUTH_USER is populated in all non-anonymous environments; you can
    determine who the user is by reading that variable. If it seems I'm suggesting
    you control application access through AD group membership, you're absolutely
    right. That's the right thing to do in this environment. There's no need to
    query AD; simply grant access to the resources (ColdFusion templates, images,
    folders, whatever) to the relevant AD group(s), and forget about it. My $0.02

    philh Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139