Comment 1 for bug 1385190

Oh, this would rock, even in simple setups I've had SSH credential problems. I would implement it as a control in the admin interface rather than a management command.

I think something synchronous would work well, rather than launching a Celery task for this. Maybe a "test connectivity" button in the archive's edit page. If the data is valid and has been saved it could try logging in (set a reasonable timeout) and dropping a test file in the archive. If the data has not been saved, prompt the user to save before using the test button.

We can make it generic enough to use with any archive, so we can also test local (mostly for file permissions) and eventually swift.

Though that deviates from the bug description; but IMHO a set of credentials in isolation is meaningless, it has to be tested in connection with the archive.