Derby
  1. Derby
  2. DERBY-3848

dblook fails to connect an authenticated database

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 10.4.1.3
    • Fix Version/s: None
    • Component/s: Tools
    • Labels:
      None
    • Environment:
    • Urgency:
      Normal

      Description

      dblook is not connecting an authenticated database.

      I create an authenticated database this way:

      1. ij
      2. connect 'jdbc:derby:dblooktest;create=true;user=test;password=test';
      3. CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication','true');
      4. CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.test', 'test');
      5. CREATE TABLE DBLOOKTESTTABLE(I INT NOT NULL PRIMARY KEY);
      6. disconnect;
      7. quit;

      And use dblook this way:

      8. dblook -d 'jdbc:derby:dblooktest;user=test;password=test';

      Then an error is reported (dblook.log contents are at the end of this description);

      Nevertheless, if I do not require authentication:

      9. CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication','false');

      Then dblook works properly:

      10. dblook -d 'jdbc:derby:dblooktest;user=test;password=test';
      11. dblook -d 'jdbc:derby:dblooktest';

      Thus, the same connection url that works in ij for an authenticated database does not in dblook.

      =========== dblook.log

      java.sql.SQLNonTransientConnectionException: Se ha producido una anomalía de autenticación de conexión. Razón: Autenticación no válida..
      at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
      at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
      at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
      at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
      at java.sql.DriverManager.getConnection(DriverManager.java:582)
      at java.sql.DriverManager.getConnection(DriverManager.java:207)
      at org.apache.derby.tools.dblook.go(Unknown Source)
      at org.apache.derby.tools.dblook.<init>(Unknown Source)
      at org.apache.derby.tools.dblook.main(Unknown Source)
      Caused by: java.sql.SQLException: Se ha producido una anomalía de autenticación de conexión. Razón: Autenticación no válida..
      at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
      ... 17 more
      – **--> DEBUG: Se ha producido una anomalía de autenticación de conexión. Razón: Autenticación no válida..

      1. dblook.log
        2 kB
        Antonio Sánchez
      2. derby.log
        4 kB
        Antonio Sánchez
      3. test.sh
        0.5 kB
        Dag H. Wanvik

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Antonio Sánchez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development