I was having a frustrating situation yesterday where the WLS console would just hang after clicking the Servers link. Naturally I go to the Unix console to tail the logs and see what’s what, and these prompts for a password keep popping up. Entering the admin password is no help.
So I went to the next natural step of rebuilding the domain (the build is scripted, and yes, I backed up the domain first) and the problem is still there!
An email to a colleague more steeped in the dark arts of server administration than I results in the suggestion that this is due to a problem with SSH (the domain uses SSH Node Manager) and tells me test it with:
ssh username@hostname
to confirm connectivity and permissions. What I get back is:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions 0755 for '/app/home/username/.ssh/id_rsa' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. bad permissions: ignore key: /app/home/username/.ssh/id_rsa Password:
With this new detail in mind, I went to an environment that was working, found it had the file permission set at 600, and preforming
chmod 600 /app/home/username/.ssh/id_rsa
Got me up and running again
© Scott S. Nelson
I later found a better solution at http://kb.mediatemple.net/questions/1626/Using+SSH+keys+on+your+server:
chmod 700 ~/.ssh && chmod 600 ~/.ssh/*