Problem
The point why this is needed is pretty simple, we can add multiple layers in front of olake to protect it but being able to change/rotate this is very crucial to meet the required security standards, one reason why this originated in the first place is the setups initially created for testing but later made to use in production still have the weaker passwords from the testing phase.
Why this didnt feel imp before is we weren't aware of any spoofing that happened on our olake deployment until today, [attaching image below]
since this we have added more layers in front of olake but to be able to change the very weak initial password would greatly increase out confidence to protect it
Solution
because i am not aware of how the ui handles security, i cant really comment on what solution i can propose, once i have greater context of it , i can try to contribute to the idea
thanks
Problem
The point why this is needed is pretty simple, we can add multiple layers in front of olake to protect it but being able to change/rotate this is very crucial to meet the required security standards, one reason why this originated in the first place is the setups initially created for testing but later made to use in production still have the weaker passwords from the testing phase.
Why this didnt feel imp before is we weren't aware of any spoofing that happened on our olake deployment until today, [attaching image below]
Solution
because i am not aware of how the ui handles security, i cant really comment on what solution i can propose, once i have greater context of it , i can try to contribute to the idea
thanks