I downloaded ejabberd for Windows, and during the setup process created the admin name and password. I'm attempting to access the admin control panel (localhost:5280/admin), and am attempting to login with the username (admin#MyServer) and password, but each time it just asks me to log in again. The server is running too, so I'm not sure what I'm doing wrong.
ejabberd 16.09 will be released shortly and will include that fix.
Ref: Here.
for now start ejabberd with this command ejabberdctl live and see the log when you try to login.
if it says in-existed account than you have to download xmpp client software from here.
After Installing this creat the admin account from this client after you have does this you will be successful is logging in the admin control.
Settings for Pidgin:
Add:
1. Protocol : xmpp
2. Username : admin
3. Domain : MyServer
4. Password : asyouwant
Advance:
1. Connect Server : localhost
donot forget to check the create this account on the server checkbox.
I used admin#nabin-pc instead of admin#NABIN-PC and got logged in successfully.
Related
I have installed gitlab server using docker compose but after the installation I am not getting a default screen where we create first Admin user. Instead of that it is asking me to enter username and password.
If I see this correctly, the gitlab_root_password should be set in the Compose file. This should then be used to log in for the first time.
Source: https://docs.gitlab.com/ee/install/docker.html#install-gitlab-using-docker-swarm-mode
I want to change the password to an specific user of a james server.
Thanks
You can connect to James Remote Administration Tool via Telnet
telnet <ip> 4555
The default credentials are login: root password: root
Once connected, simply run this command:
setpassword [username] [password]
Better : using the commandline client provided by the project.
It use JMX under the hood. The CLI is packages with every distribution of the server. (you can even execute it via maven from here : https://github.com/apache/james-project/tree/master/server/container/cli)
Then, fnkrm is right, you should go for setpassword.
Alternatively, on 3.0-betax we provide optional admin REST APIs. https://github.com/apache/james-project/tree/master/server/protocols/webadmin . Have a look to the corresponding docker images if interested.
Cheers,
Benoit.
We use Mattermost using the 'Production Docker' setup as described in Mattermost documentation. For authentication, we federate using GitHub:Enterprise.
To setup our Mattermost team, I imported the whole Slack history. This lead to the problem that everyone who did not yet log into Mattermost via GitHub:Enterprise was not able to login. Mattermost helpfully returned the error message
"An existing user is already attached to your gitlab account"
How can I fix this issue without having to setup a new Mattermost instance and force everyone to login once before importing the Slack data?
Prerequisites
In order for this to work, you need
GitHub:Enterprise Administrator permissions
On the Mattermost machine, either root permissions or an account that is allowed to control docker, and, if psql is not installed, a way to install the psql command-line tool.
Steps
ssh into the Mattermost vm/machine (where the mattermost docker containers are running).
Change to an account with docker permissions (root; or the account you setup during Mattermost installation; or ... )
Use docker ps and note the hash of the container mattermostdocker_db. We will assume it starts with 5c23.
Run docker inspect 5c23 | grep IPAddress. Note the IP address of the container. We will assume it is 172.17.0.2.
Ensure that the psql commandline tool is installed on the machine where mattermost/docker is running.
On debian: apt-get install postgresql-client
Connect to the mattermost db of postgresql running inside the docker container:
psql -h 172.17.0.2 -p 5432 -d mattermost -U postgres -W
The (default?) password seems to be postgres.
Verify that a user account with the correct email exists. Assume the email of the account that has the problem is 'john#example.com`
mattermost-# select email, authdata from users where email = 'john#example.com';
Connect to GitHub:Enterprise and open the admin console. We will assume the local github enterprise instance is at https://github.example.com.
Click on the rocket symbol, or
https://github.example.com/stafftools
Click on all users and find the user that cannot login. We assume the github username is john, which would correspond to https://github.example.com/john
Visit the stafftools user security page for that user.
https://github.example.com/stafftools/users/john/security
Click on the 'Search logs' link under the 'Audit logs' header. This will open a page with a query field. On this page, you will find the internal github user number for that user. Note this number. We will assume the number is 37.
Back in the psql console, update the user entry with the correct number:
update users set authservice = 'gitlab', authdata = '37' where email = 'john#example.com' ;
Exit the psql console with \q:
mattermost-# \q
Done. The user can now log into Mattermost with GitHub:Enterprise user authentication.
Notes
Don't forget to complete each statement in psql with a ;
It's gitlab, not github, even if you use GitHub:Enterprise
Tested with Mattermost 3.0, GitHub:Enterprise 2.6.2
Admin console is listening at http://localhost:9090 and when I try to login it goes to index.jsp page but that page is blank, what could be reason.
server is connected to database and successfully configured and added tables in database. Using Windows OS, and database is MYSQL which is running at local host port 3306.
I also had the same problem and than I downloaded Open fire 3.9.2 and followed steps at this link and it worked for me. https://community.igniterealtime.org/docs/DOC-1200
before this I was using 3.9.3.
I am using Lion 10.8.2, and in sudoers i made like this: username ALL=(ALL) NOPASSWD, the username is my computer user... but still now prompts password.. What to do ?
If you are talking about the Pop Up window while starting the servers then you cannot get away with it. An API(Don't know which exactly) is used to start the Apache server which requires administrator privileges. sudo in the terminal and this API call is different, editing any files won't help.
Port 80, default port of Apache is a Well-Known port which requires admin privileges as written in the link. So they must have forcefully added the API Call for starting the server.