Allow specifying SECRET_KEY_URI, similar to INTERNAL_TOKEN_URI (#19663)
Only load SECRET_KEY and INTERNAL_TOKEN if they exist. Never write the config file if the keys do not exist, which was only a fallback for Gitea upgraded from < 1.5 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
This commit is contained in:
parent
04e97b8311
commit
3d10193be2
7 changed files with 52 additions and 51 deletions
|
@ -364,7 +364,7 @@ func loadOrCreateSymmetricKey() (interface{}, error) {
|
|||
return nil, err
|
||||
}
|
||||
|
||||
setting.CreateOrAppendToCustomConf(func(cfg *ini.File) {
|
||||
setting.CreateOrAppendToCustomConf("oauth2.JWT_SECRET", func(cfg *ini.File) {
|
||||
secretBase64 := base64.RawURLEncoding.EncodeToString(key)
|
||||
cfg.Section("oauth2").Key("JWT_SECRET").SetValue(secretBase64)
|
||||
})
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue