Hi

I notice that recently you have put in place tools which force a strong username and password for staging sites. Previously the username and password could be anything at all.

I'd like to suggest that you should roll back this change. Although (of course!) I am wholly in agreement that passwords should be strong in almost all cases, I believe that staging sites should have an option for this not to be the case.

Why?

1. Mainly - because the most obvious use case here is for sharing with a client. Whereas we could previously have for instance "demo" and client name as u/p (easily memorable both for us and for clients) - now we have to create and constantly re-share passwords when the client can't remember how to get in

2. Password managers don't normally offer the option to save popup NTCR-style passwords like this so we have to resort to logging into the CloudWays interface to see what is set

3. The actual thing that is being passworded isn't very sensitive - and actually shouldn't be. A staging site is almost always just a copy of a live site where tech changes have been made. In our case, the only reason for passwording it in the first place is that we don't want Google and other bots spidering it - it isn't sensitive at all.

4. If you left this option so that you had a warning there about weak passwords - "Are you SURE you don't want a strong password for this?" then IT people like myself can make a call on whether to set it as strong or weak, depending on use case. Mandating it in the way you do is preaching to an already tech-savvy audience!