[ 
https://issues.apache.org/jira/browse/AIRFLOW-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914280#comment-16914280
 ] 

ASF GitHub Bot commented on AIRFLOW-5145:
-----------------------------------------

ashb commented on pull request #5761: [AIRFLOW-5145] take false is_encrypted 
choice away from user
URL: https://github.com/apache/airflow/pull/5761
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> rbac ui presents false choice to encrypt or not encrypt variable values
> -----------------------------------------------------------------------
>
>                 Key: AIRFLOW-5145
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5145
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: ui
>    Affects Versions: 1.10.3, 1.10.4
>            Reporter: Jon Stern
>            Priority: Minor
>
> With webserver rbac=True and core fernet_key set, variable values are always 
> encrypted, but they are only marked as is_encrypted = true in the database if 
> the user explicitly checks theĀ *Is Encrypted* checkbox on the variable create 
> screen. If a variable is set up this way, then it is not correctly displayed 
> in the UI and calls to Variable.get return the cipher text instead of the 
> decrypted value.
> Workarounds are:
>  * Explicitly check the box in the UI if you know you've got a fernet key set 
> up.
>  * Edit the variable after creation and re-enter the value. On the edit 
> screen there is no checkbox, and is_encrypted is properly set to true on 
> saving.
> Since the only right answer is is_encrypted = true, it seems like the 
> checkbox should not be displayed (as in the edit screen and as in the 
> non-rbac create screen)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to