16 character password limit; need work-around

Ask a Question related to Coldfusion Database Access, Design and Development.

  1. #1

    Default 16 character password limit; need work-around

    Looks like CF7 has a documented 16 character limit on datasource passwords. Our
    production server password is 18 characters.

    I brought this up on the cftalk mailing list, and the suggestion was made to
    try a third party JDBC driver. I tried the Microsoft JDBC driver, as well as
    jDTS. Both exhibited the exact same behavior; my sa login (which is under 16
    chars) worked, but the regular login did not. The exact error is:

    Connection verification failed for data source: BULLHORN_MASTER
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
    JDBC][SQLServer]Login failed for user 'bullhorn1'.
    The root cause was that: java.sql.SQLException: [Microsoft][SQLServer 2000
    Driver for JDBC][SQLServer]Login failed for user 'bullhorn1'.

    ColdFusion appears to be truncating the password at 16 characters before it
    passes is to JDBC, regardless of the driver used. When I configure this new
    driver to use the sa username/password, it works great. When I change just the
    username and password to our regular login (bullhorn1), I get a "Login failed
    error". It's not saying the password is too long, or that JDBC is rejecting the
    password due to length, it's saying login failed. This leads to the assumption
    on my part that CF is truncating or otherwise altering the password before it
    hands it off to the driver.

    Also interesting to note is that even when using the custom JDBC drivers and
    specifying the "other" driver type, it warns you on that definition screen that
    there is a 16 character limit.

    I'm ready to call out the CF development team. True, it's documented right
    there in the app, but this could very well throw a huge monkey wrench into our
    CF7 plans, for a very stupid issue. Please, anyone else have an ideas?

    Before you say "just change the password". That is not an option. We are
    talking about 30 different SQL Servers, and the password is probablly hardcoded
    in a bunch of places. Not our actual site code, but doubtless many little
    utilities we have written over the years. Regardless, JDBC drivers can handle
    passwords longer that 16 character just fine, this is strictly a ColdFusion
    "feature".

    quasigenx Guest

  2. Similar Questions and Discussions

    1. Telnet character limit?
      I have a perl telnet script which sends commands to a remote VAX host. The commands get wrapped around at 80 characters, which cause them to get...
    2. How to limit character output with CFML
      Hi! I need a bit of help... I'm trying to figure out how to limit CFML output to a certain number of characters... On a given page on our site,...
    3. Dynamically limit character output to fit space
      Here is the situation: I have a table that has 5 columns. I want each column to have a width of 20%. Here is the tricky part, for a few of the...
    4. TOC character limit, glitch?
      In creating a table of contents in InDesignCS, it seems to cut entries off at 256 characters. I NEED all of those characters. Is there a setting...
    5. CDONTS-Sending HTML mail-8000 character limit
      Hi all, I have seen a few messages about this in the archives, but none provide a comprehensive answer. Basically, I want to use CDONTS mail...
  3. #2

    Default Re: 16 character password limit; need work-around

    Since this post, I have tried a couple of other options, to no avail.

    1. I tried using the API admin tool to set a longer password. This created the
    datasources ok, but exhibited the same behavior or truncatint the password
    passes to JDBC.

    2. I tried ODBC, and was flabbergaster to fing that it had the same
    limitation. I even tried trusted connection ODBC, but that looks like it would
    involve re-installing SQL server in mixed authentication mode. Forget that.

    At this point, I have literally no fallback position besides:

    A. Changing the password on all 30 SQL Server instances.
    B. Reverting my shiny new code back to CF5.5 and never using CF7 again.

    Any developers/support reps want to weight in on this?

    quasigenx 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