Derby
  1. Derby
  2. DERBY-5299

Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: 10.8.2.2, 10.9.1.0
    • Component/s: Documentation
    • Labels:
      None
    • Urgency:
      Normal
    • Issue & fix info:
      Patch Available
    • Bug behavior facts:
      Security

      Description

      It is possible to deploy the first version of your Derby-powered application without enabling authentication and authorization. In a later version of your application, you may want to boost security by enabling these features. It would be good to tell users what they should expect when they enable authentication/authorization on a legacy database.

      1. 5299_setup.sql
        0.4 kB
        Rick Hillegas
      2. 5299_withAuth.sql
        2 kB
        Rick Hillegas
      3. derby-5299-01-aa-securingOldDatabase.diff
        5 kB
        Rick Hillegas
      4. derby-5299-01-aa-securingOldDatabase.tar
        40 kB
        Rick Hillegas
      5. derby-5299-01-ab-securingOldDatabase.diff
        5 kB
        Rick Hillegas
      6. derby-5299-01-ab-securingOldDatabase.tar
        40 kB
        Rick Hillegas

        Activity

          People

          • Assignee:
            Rick Hillegas
            Reporter:
            Rick Hillegas
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development