Unlike cienaCesRadiusUserLoginAuthKey, which accepts a plaintext secret that always reads back blank, this object explicitly expects a pre-encrypted value and, notably, actually returns that encrypted value when read back. That's a meaningfully different security model the admin needs to understand before assuming this field behaves like the other, always-blank-on-read RADIUS key objects in this MIB. For example, an automation script provisioning multiple devices identically could safely read back and copy this encrypted secret between devices, something it explicitly cannot do with cienaCesRadiusUserLoginAuthKey.