veops / cmdb

CMDB: configuration and management of IT resources
https://veops.cn/cmdb
GNU Affero General Public License v3.0
1.44k stars 370 forks source link

[Bug]: 保存密码失败: Invalid key size (0) for AES. #288

Open hutong236 opened 10 months ago

hutong236 commented 10 months ago

Contact Details

No response

This bug is related to UI or API?

UI

What happened?

数据类型选择密码后,保存数据后,报错:保存密码失败: Invalid key size (0) for AES.

Version

2.3.6

What browsers are you seeing the problem on?

Microsoft Edge

Relevant log output

No response

pycook commented 10 months ago

@hutong236 你有初始化密码的设置吗 密码存储是做了升级的 要存储密码需要初始化一次,方法可看公众号的发版的文章

taoyang987 commented 6 months ago

https://mp.weixin.qq.com/s/Wp-fHIzfmcZWFVrx2vHR2g 公众号密码的文章在这

fxkjnj commented 6 months ago

根据公众里的文章:https://mp.weixin.qq.com/s/Wp-fHIzfmcZWFVrx2vHR2g

如果是容器docker-compose 部署方式: 1、进入到cmdb-api 容器里,初始化: flask cmdb-inner-secrets-init 保存所有秘钥到本地小本本上

2、修改docker-compose.yml 文件,修改cmdb-api 那块内容,添加INNER_TRIGGER_TOKEN = ""

` command:

3、重启容器,创建密码验证

NemoAllenZ commented 5 months ago

根据公众里的文章:https://mp.weixin.qq.com/s/Wp-fHIzfmcZWFVrx2vHR2g

如果是容器docker-compose 部署方式: 1、进入到cmdb-api 容器里,初始化: flask cmdb-inner-secrets-init 保存所有秘钥到本地小本本上

2、修改docker-compose.yml 文件,修改cmdb-api 那块内容,添加INNER_TRIGGER_TOKEN = ""

command: - /bin/sh - -c - | sed -i "s#USE_ACL = False#USE_ACL = True#g" settings.py sed -i "s#INNER_TRIGGER_TOKEN = ''#INNER_TRIGGER_TOKEN = 'xxxxxxxxxxxx'#g" settings.py

3、重启容器,创建密码验证

添加到这里之后,重启cmdb-api容器,刷新页面,问题还是一样 image

fxiang21 commented 5 months ago

根据公众里的文章:https://mp.weixin.qq.com/s/Wp-fHIzfmcZWFVrx2vHR2g 如果是容器docker-compose 部署方式: 1、进入到cmdb-api 容器里,初始化: flask cmdb-inner-secrets-init 保存所有秘钥到本地小本本上 2、修改docker-compose.yml 文件,修改cmdb-api 那块内容,添加INNER_TRIGGER_TOKEN = "" command: - /bin/sh - -c - | sed -i "s#USE_ACL = False#USE_ACL = True#g" settings.py sed -i "s#INNER_TRIGGER_TOKEN = ''#INNER_TRIGGER_TOKEN = 'xxxxxxxxxxxx'#g" settings.py 3、重启容器,创建密码验证

添加到这里之后,重启cmdb-api容器,刷新页面,问题还是一样 image

我本地重新测试一遍是没有问题的,检查一下是否是用的root token,如下图,然后进入到容器中在当前目录下的settings.py中确认下token是否预期的一致 image