Context: Setting up Shield on my local machine for a 1 node Elasticsearch
Machine: Mac OSX 10.9.5
After installing Shield, I tried adding admin users but failed to do so because initially I did not restart my ES. During this attempt, I tried a bunch of username and password combinations(My bad here).
After I was pointed out that I had to restart ES before creating any users, I did so. Now, everytime I open localhost:9200 on my browser, I am required to provide a username and password.
I have tried most of the combinations that I 'attempted' to create earlier, but non seems to be the right one.
Upon running the bin/shield/users, it shows that I have one user which is my machine name. Tried again a bunch of possible passwords that I could think of, but nothing seems to be the right one. Below is the error I'm getting
{"error":"AuthenticationException[unable to authenticate user [username]
for REST request [/_shield]]","status":401}
So, any idea on how I could reset the password or the delete the user entirely ??
Use the esusers userdel username command to delete that username and add another one of your choice.
Related
I want to make a script that asks the user for username and password and uses these for a few things at once, including connecting to OpenVPN without needing to either
store the password on the disk
ask the user for the data many times over
for example you can run net use with user and password to mount shares, however openVPN seemingly only has an option to pass a file with username and password.
On Linux there seemingly are solutions like this, however I don't seem to find anything similar for windows yet.
Is there a solution?
I am having issues with the UI prompt which is asking me to enter my password to access the keychain credentials for proxy.
My mac is used in a local network without internet access, so I need to setup a proxy connection with username and password for browsing and all other mac services. I configured proxy including authentication in network settings. When browsing, chrome asks me once to enter credentials and it is working fine after then. If any other system service tries to connect, I am getting prompted to enter my password so proxy credentials can be fetched from keychain. I also changed the keychain entry to allow all applications to access it, but the prompt keeps on asking and asking and asking for my password. The next time, the keychain entry is changed back again to allow only some applications. Looks like it is always overriding the old entry.
Any ideas how I can fix that? Unfortunately I do not have any access on configuration of the proxy server or to change any parameters there, if it is a configuration issue of the proxy server. But there has to be a solution, I do not think entering the password hundreds of times a day can be an accepted solution.
My Mac is newly setup and running macOS Big Sur 11.2.1
Have you seen this answer https://apple.stackexchange.com/questions/106742/mac-username-password-for-proxy-settings-keep-resetting-by-itself? Usually you can move the password item in the keychain to the System section rather than the login section and this fixes the issue.
I have a similar issue but I am in a corporate environment and my issue seems to be related to NTLM https://apple.stackexchange.com/questions/292835/how-to-store-proxy-credentials-on-macos-so-they-are-used-by-system-services?rq=1
I installed postgresql on windows and while the installation it asks to make a user for the account.This made a new windows user in my computer called postgres, I have created a password for it as well.
Now I want to run psql on windows command line, it asks for a password (without mentioning the user) and always gives me back the error: psql: FATAL: password authentication failed for user "Ash". Even though I have put my accounts password many times.
using pgadmin I changed the user "postgres" to "Ash" but I have yet to remake the password. I followed the steps here: I forgot the password I entered during postgres installation (I rather types host all 127.0.0.1/32 trust because I am on windows), but when running psql again so that I can change the password I get the error: psql FATAL:could not load pg_hba.conf. All together.
Why can it not load? All I did was add an extra authentication option.
Also, is the windows user separated from a postresql user or are they the same(depend on each other)?
Edit:
As you can see, it did not give me the option to choose if Aisha should be a superuser or not. or the other options for that matter.
I also used pgadmin||| to create a new user but the same error pops up:
The user does not exist so why does it do this?
The user on your machine has nothing to do with the user on PostgreSQL. The installer just creates an account and a PostgreSQL role with the same name and password (which in my mind is a bad idea), but they're not related in any way. The Windows user is used to run the server, the PostgreSQL role is used inside the database.
So you should first access the server with the user postgres and then create a user for yourself. Don't change the username inside the server, or the server's running user! Just create a new username and grant it the permissions you need.
You can use psql -U postgres to connect to the server and it'll ask for the password.
Check the permissions for pg_hba.conf, the postgres user must have permissions for it. If you only edited it as an admin, it should be ok, but if you took permissions or anything else, it may mess it up.
createuser is a command-line utility. Use CREATE USER username WITH PASSWORD 'fred'; or similar at the SQL level in psql. Note the semicolon.
What you're doing in your screenshot is starting to write an SQL command beginning with createuser, but never sending it to the server to run because there's no semicolon terminator. So you never get the error that would tell you it doesn't make sense to do that.
I had exactly the same problem and this line solved it;
createuser --createdb -U postgres --login -P 'your_new_user'
#sami-kuhmonen was right, but his approach of solving the problem did not work for me.
This can also happen if the encryption for stored passwords does not match the encryption for connections as defined in postgresql.conf ang pg_hba.conf
For example, if postgresql.conf has:
password_encryption = md5
but pg_hba.conf has:
host all all 10.0.0.110/24 scram-sha-256
Then all connections on the 10.0.0.110 interface will have the 'FATAL: password authentication failed error'.
Remember that if you change either of these files you will need to restart postgresql and if you change the password encryption in postgresql.conf you will need to change the passwords for all of the users.
Hope this helps some others with this problems.
I was having the same error. I get to solve it by locating the "pg_hba.conf" file. You can use this navigation:
C:\Program Files\PostgreSQL\14\data\pg_hba.conf
Then inside the file, changed all the methods "scram-sha-256" to trust and problem was solved.
I have been trying to create VPN connection programmatically, I referred to this link
Its working fine but when user installs the profile, its asking VPN password again. I’m not interested in asking the user to set the password. I need to set password automatically without getting it from user. How to do this? (I saw some app that has done this already).
I have followed Amazon instructions to the letter and it does not work.
ec2-api-tools-1.3-34128 - this is the api tools that I got from Amazon
Set it up following instructions. Checked everything to make sure I follow instructions. When I try to use it, I only get: "invalid.blabla" depending on what command do I try to use.
Anybody with this problem?
I deleted all my instances and all key pairs.
Created new ones (instance and key pair).
Setup putty all over again like instructions say I should do
(creating .ppk file and everything).
Still the problem remains.
When I try to connect to my ec2 instance using putty
I get "login as : " ????????
Also, I am using windows vista.
Is this a problem.
Thanks
Had this same problem. I found that in putty I had to do three things (only 2 of which are mentioned in the amazon guide at http://docs.amazonwebservices.com/AmazonEC2/gsg/2007-01-19/putty.html)
provide the converted private key in the ssh -> Auth section
provide the dns name or IP
go to Connection -> Data and enter "ec2-user" as the Auto-login username
Hope this saves someone else 20 mins!
Did you make sure that you put "root" as the auto-login account in the "Data" section?
A mistake I made than gave me the same error message was setting
"root#ec2-.eu-west-1.compute.amazonaws.com" as the value in the "Host Name (or IP Address)" field in putty.
You need to specify "ubuntu#ec2-.eu-west-1.compute.amazonaws.com".