Problem
When using the mcs-lab-auditor plugin, after the workshop account is redeemed and the password is changed during first login, the plugin later prompts the user to manually enter the password again. This is unnecessary and disruptive — the password was generated by the plugin itself during the account setup flow and should already be cached via DPAPI.
Expected behavior
The plugin should always use the DPAPI-cached password after initial account setup. The user should never be asked to type in the password that the plugin itself generated.
Current workaround
The \�ccount_prompt_mode\ setting in \config/judge-config.yml\ (line 43) was changed from \�lways\ to \only_if_expired\ to prevent re-prompting. This should be the default behavior, not something the user has to configure manually.
Suggested fix
- Change the default value of \�ccount_prompt_mode\ from \�lways\ to \only_if_expired\
- Only prompt for the password if the cached credential is missing or the session has genuinely expired
- The \�lways\ mode should still exist as an option but should not be the default
Problem
When using the mcs-lab-auditor plugin, after the workshop account is redeemed and the password is changed during first login, the plugin later prompts the user to manually enter the password again. This is unnecessary and disruptive — the password was generated by the plugin itself during the account setup flow and should already be cached via DPAPI.
Expected behavior
The plugin should always use the DPAPI-cached password after initial account setup. The user should never be asked to type in the password that the plugin itself generated.
Current workaround
The \�ccount_prompt_mode\ setting in \config/judge-config.yml\ (line 43) was changed from \�lways\ to \only_if_expired\ to prevent re-prompting. This should be the default behavior, not something the user has to configure manually.
Suggested fix