You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The KRCI Portal's Configuration section allows for the saving of secrets, prompting some browsers to offer the option to save these secrets locally. This poses a security risk, as sensitive information could be unintentionally stored in the browser. This task aims to investigate the cause of this behavior and implement a solution to prevent browsers from offering to save secrets entered in the Configuration section.\nh4. Acceptance Criteria\n- Browsers no longer offer to save secrets when entered in the Configuration section of the KRCI Portal.\n- Sensitive data entered into the portal cannot be inadvertently saved or auto-filled by the browser.\n- The solution does not negatively impact the user experience or functionality of the Configuration section.\n- Comprehensive testing is conducted across multiple major browsers (e.g., Chrome, Firefox, Safari, Edge) to ensure the issue is resolved.\nh4. Implementation Plan\n- Investigate how browsers detect input fields for saving or auto-filling data and identify the cause of the prompt when secrets are saved in the KRCI Portal.\n- Explore possible solutions, such as modifying input field attributes (e.g., autocomplete="off"), to prevent browsers from offering to save secrets.\n- Implement the chosen solution in the Configuration section of the KRCI Portal.\n- Conduct thorough testing across different browsers to verify that the prompt to save secrets is effectively disabled.\n- Roll out the update to the production environment upon successful testing.
The text was updated successfully, but these errors were encountered:
The KRCI Portal's Configuration section allows for the saving of secrets, prompting some browsers to offer the option to save these secrets locally. This poses a security risk, as sensitive information could be unintentionally stored in the browser. This task aims to investigate the cause of this behavior and implement a solution to prevent browsers from offering to save secrets entered in the Configuration section.\nh4. Acceptance Criteria\n- Browsers no longer offer to save secrets when entered in the Configuration section of the KRCI Portal.\n- Sensitive data entered into the portal cannot be inadvertently saved or auto-filled by the browser.\n- The solution does not negatively impact the user experience or functionality of the Configuration section.\n- Comprehensive testing is conducted across multiple major browsers (e.g., Chrome, Firefox, Safari, Edge) to ensure the issue is resolved.\nh4. Implementation Plan\n- Investigate how browsers detect input fields for saving or auto-filling data and identify the cause of the prompt when secrets are saved in the KRCI Portal.\n- Explore possible solutions, such as modifying input field attributes (e.g.,
autocomplete="off"
), to prevent browsers from offering to save secrets.\n- Implement the chosen solution in the Configuration section of the KRCI Portal.\n- Conduct thorough testing across different browsers to verify that the prompt to save secrets is effectively disabled.\n- Roll out the update to the production environment upon successful testing.The text was updated successfully, but these errors were encountered: