klesh opened a new issue, #2032:
URL: https://github.com/apache/incubator-devlake/issues/2032

   ## Describe the bug
   In the current jira implementation, we encrypt `basicAuth` before we store 
it in the database, and the encryption key is created and saved to the `.env` 
file if it doesn't exist.
   This is OK, well, in most cases. but occasionally, due to debugging or 
accidental reasons, we have to recreate `.env`, which would cause `basicAuth` 
undecryptable, and the sensible way to address the problem is to let the 
developer/user be able to update the `basicAuth` with newly generated `encKey`.
   
   
   ## To Reproduce
   Steps to reproduce the behavior:
   1. Create a new jira connection, make sure it is connected
   2. Shutdown devlake, delete `.env`file, and recopy from `.env.example`
   3. Fire up devlake, and reload config-ui
   4. See error
   
   ## Expected behavior
   1. jira connections should be able to be displayed
   2. I should be able to update the `basicAuth` to fix the connection
   
   
   ## Screenshots
   
![image](https://user-images.githubusercontent.com/61080/170968730-11a876fa-aace-47dc-8d0c-c2596ea92fe0.png)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to