Admin password change results in server error

[John O'Donnell]

Summary

User admin trying to change their password results in 500 Internal Server Error response.
Discovered from CI failures in cyberark/conjur-openapi-spec.

Steps to Reproduce

1. Start the development environment

   cd dev
   ./start
   

   Start the Conjur server from the resulting shell with conjurctl server

2. Use the Conjur client as admin, and attempt to set/change the password

   cd dev
   docker-compose exec client /bin/bash
   

   From the resulting shell, log in as admin and attempt to set/change the password

   conjur user update_password --password='Ch@ng3Password!'
   

   This step will output a mountain of HTML, containing the below stack trace(see Actual Results), ending with:

   error: 500 Internal Server Error
   

Expected Results

admin should be able to set/update their password when authenticated.

Actual Results

admin requesting a password change receives a 500 Internal Server Error response, with a mountain of HTML containing the following Conjur stack trace:

RuntimeError (Resource not found for dev:user:admin)
app/models/role.rb:126:in `resource'
app/controllers/credentials_controller.rb:41:in `update_password'
app/controllers/application_controller.rb:79:in `run_with_transaction'
lib/rack/remove_request_parameters.rb:26:in `call'
lib/rack/default_content_type.rb:68:in `call'

Reproducible

• Always
• Sometimes
• Non-Reproducible

Version/Tag number

• The bug was found in integration tests in the cyberark/conjur-openapi-spec repo, which uses the image cyberark/conjur:edge.
  • I've confirmed that the integrations tests pass when using cyberark/conjur:latest, so this is a recent, unreleased bug.
• I've confirmed the behavior using the dev environment on the latest version of master branch.

Environment setup

• Can you describe the environment in which this product is running? Is it running on a VM / in a container / in a cloud?
• Which cloud provider? Which container orchestrator (including version)?
• The more info you can share about your runtime environment, the better we may be able to reproduce the issue.

Additional Information

Add any other context about the problem here.