Uploaded image for project: 'Archiva'
  1. Archiva
  2. MRM-1679

Changing admin password in Continuum using shared external "users" database causes Archiva security workspace to become stale

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4-M3
    • Fix Version/s: None
    • Component/s: Design, system, Users/Security
    • Labels:
      None
    • Environment:

      Description

      I'm sharing the "users" database between Archiva and Continuum. I switched over to PostgreSQL v9.2 on my laptop to mirror the Archiva/Continuum/PostgreSQL setup I've installed on a server. I wanted the same password for the admin account as the admin account that's set up on the server, so I changed the password to the admin account using Continuum.

      I was able to then log out and log in with the new password in Continuum. Upon verifying that I could log in as admin to Archiva with the new password, I discovered that I was not able to log in.

      The remedy was to navigate to C:\apache\tomcat_base_archiva\data\jcr\workspaces and delete the 2 default workspaces "security" & "default". I know that a workspace's workspace.xml can become stale if something with repository.xml is changed. Deleting it will prompt Apache Jackrabbit to regenerate a new workspace.xml. Whether I have to delete BOTH "security" and "default"...I don't know. Whatever the case may be, that's worked for me.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Chris Harris Chris Harris
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: