Is there a configuration setting in RHEL/CentOS thru which "Retype new password" can be disabled while changing user password.
Thanks.
Related
I'm running grafana locally on my windows 10 computer using the grafana-8.0.2.windows-amd64 installer.
I'm having issues resetting my password - username: admin password: admin doesn't work and I don't remember what I set it to. I've navigated to the /GrafanaLabs/grafana/bin/ folder in the command prompt and run the command: grafana-cli admin reset-admin-password 'admin'
which returns ←[31mError←[0m: ←[31m✗←[0m failed to load configuration: failed to initialize file handler: open C:\Program Files\GrafanaLabs\grafana\data\log\grafana.log: Access is denied.
I've read so many potential solutions and tried the SQLite one referenced here - https://community.grafana.com/t/how-do-i-reset-admin-password/23/2 and while this doesn't give me an error message, it does not allow me to log in even after restarting the Grafana in "Services" through the OS.
Very simply, you need to run the command prompt as an administrator. The above instructions will work as is but the password will literally be 'admin' rather than admin. Use double quotes if you wish to have spaces in your password as shown below.
grafana-cli admin reset-admin-password "admin password"
I have a Public Cloud instance via OVH. I reinstalled my computer without backing up my ssh-key. I also forgot the root password for the server. I do have access to my Public Cloud control panel and rebooted with rescue mode.
However, when I change my root password (via the noVNC console) and then reboot to my Ubuntu disk, the new password is incorrect.
The passwd command returns: passwd: password updated successfully!.
But then I can't login as root with the new password after exiting rescue mode.
What am I doing wrong?:
By default, password login for root and the default user is not possible by ssh. If you used a key, you'll need to replace that key via the Rescue Mode. You can follow that guide to do that : Replacing your lost ssh key pair
Also, remember that you need to mount your partition containing your OS before doing any modification. The step are well describe in the OVH documentation here : Put an instance in Rescue Mode
When you are in rescue mode and you change the password with passwd, you change the password for the rescue mode only !
If you want to change you "normal OS" password from the rescue mode, you first need to chroot into the partition holding your "normal OS" and then use passwd there to change your password:
$ chroot /mnt/vdb1/
$ passwd
More details in the official doc
I'm trying to start a remote desktop connection to a computer with a user that doesn't have a password, using Powershell. The cmdkey command does not seem to accept an empty password, but asks me for a password with a prompt.
I need to launch the remote desktop from a Powershell-script as it needs to connect to any of several computers at will, so saving the credentials to Remote desktop is not an option.
I have tried using stuff like "", $null, """", "^", ` but none of these work, they are either not a password at all, are the wrong password or just freeze the Powershell-script. The same exact code works just fine for an account that has a password on the same machine.
$username=
$IPAddress=
cmdkey /generic:$IPAddress /user:$username
mstsc /v:$IPAddress /admin
Start-Sleep -Seconds 1
cmdkey /delete:"LegacyGeneric:target=$IPAddress"
The script either asks for the password, or the remote desktop prompts for it, but then accepts just pressing "Ok" with an empty password, or the whole script freezes in some cases.
It should just connect as the empty password is correct.
Windows will not allow the logon over a network with a blank password. However, there is a registry setting you can do on the target machine that disables this behaviour:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LimitBlankPasswordUse"=dword:00000000
A 'cleaner' way to set this is by using the Group Policy Editor (gpedit.msc) on the target machine.
Navigate to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options and search for option Accounts: Limit local account use of blank passwords to console logon only
Double-click this option and check Disabled.
From then on, you should be able to remote log on to that computer with a blank password.
Note: this setting of course provides a security risk.
Read about Accounts: Limit local account use of blank passwords to console logon only
I'm able to connect to a remote WAS 8.5.5 deployment manager profile after supplying the user/pass from my local WAS 8.5 install. Given below is a typical wsadmin command...
./wsadmin.sh \
-lang jython \
-conntype SOAP -host myRemoteWASHost -port 12345 \
-user wasAdminUser -password wasPassword
How can I connect to remote password less; using the UserId and (xor) Password already populated in the remote WAS Profile soap.client.props file?
Put that userid and password in to soap.client.props in the profile from where you start the wsadmin tool. You may need to create new dummy local profile to not clash with your local profile, if the profile from where you run the wsadmin has different username/password.
How to reset the password required for "cf login". Note that Bluemix login password doesn't work here. I think it is separate password.
I am using below command which need password and I don't it.
cf login -a https://api.w3ibm.bluemix.net
i think it's not possible with cf or bx commands. Go with your browser to www.bluemix.net enter your id (email) and select "forgot your password" on the next page.