Two problems:
1. `CONFIG_TOML_VERSION` was not bumped in `abra.sh` (this is an easy fix)
2. ENC_KEY upgrade does not work
On the second problem:
I followed the nice upgrade guide in the release notes, but when trying to log in I get the following error:
```
ERROR rauthy_handlers::oidc: CryptrError::Keys(EncKey ID does not exist)
```
This is what I have set in my .env file:
```
SECRET_ENC_KEYS_A_VERSION=a1 # generated=false
SECRET_ENC_KEYS_B_VERSION=b1 # generated=false
ENC_KEY_ACTIVE="a1"
```
And the secrets should have been inserted correctly
@cyrnel @decentral1se
I'm not sure on the situation of this specific version, any update @p4u1?
It seems like things have progressed in the meantime due to the good work of @3wordchant.
> https://git.coopcloud.tech/coop-cloud/rauthy/commit/eecfe6239cb7f204ebd35f39a8a77ae07e71ab60
I'm not sure on the situation of this specific version, any update @p4u1?
@p4u1 hold that thought, I'm in the middle of this migration and the instructions are quite confusing and potentially broken. I am restoring and trying again. I will try to improve the docs... what a gnarly migration 🙈
@p4u1 hold that thought, I'm in the middle of this migration and the instructions are quite confusing and potentially broken. I am restoring and trying again. I will try to improve the docs... what a gnarly migration 🙈
No wait, it works, it's just confusing as fuck. The ID of the encryption key is used as the ID of the secret from the abra side of things. It's then used in the config as follows 👇
This is a sort of "abuse" of the usual versioning approach to pass the ID into the config... 🙈
So, it's all correct, it just takes full energy brain to understand.
Good Luck ™️
No wait, it works, it's just confusing as fuck. The ID of the encryption key is used as the ID of the secret from the `abra` side of things. It's then used in the config as follows 👇
https://git.coopcloud.tech/coop-cloud/rauthy/src/commit/eecfe6239cb7f204ebd35f39a8a77ae07e71ab60/config.toml.tmpl#L27-L28
This is a sort of "abuse" of the usual versioning approach to pass the ID into the config... 🙈
So, it's all correct, it just takes full energy brain to understand.
Good Luck ™️
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two problems:
CONFIG_TOML_VERSIONwas not bumped inabra.sh(this is an easy fix)On the second problem:
I followed the nice upgrade guide in the release notes, but when trying to log in I get the following error:
This is what I have set in my .env file:
And the secrets should have been inserted correctly
@cyrnel @decentral1se
I did not get far enough to try this upgrade, so thanks for smoking this out @p4u1.
@cyrnel any ideas on the 2nd problem?
It seems like things have progressed in the meantime due to the good work of @3wordchant.
I'm not sure on the situation of this specific version, any update @p4u1?
Will try again in a couple of days
@p4u1 hold that thought, I'm in the middle of this migration and the instructions are quite confusing and potentially broken. I am restoring and trying again. I will try to improve the docs... what a gnarly migration 🙈
No wait, it works, it's just confusing as fuck. The ID of the encryption key is used as the ID of the secret from the
abraside of things. It's then used in the config as follows 👇This is a sort of "abuse" of the usual versioning approach to pass the ID into the config... 🙈
So, it's all correct, it just takes full energy brain to understand.
Good Luck ™️
@p4u1 it's resolved?
Yes