I have 40 users in my sonarqube instance.
After updating to Sonarqube 6.5 in Administration/Security/Users there is only Administrator.
Sonarqube connected to PostgreSQL database and table users contains all 40 users. Also they can login. Creating missing users fails with message: An active user with login 'XXXX' already exists.
I tried REINDEX DATABASE sonarqube; with no result.
How can I solve this problem?
The list of users is by default not shown completely in newer versions of SonarQube. Start typing a user's name or email in the filter input box to find the users you are looking for.
While a list of 40 users would be easy to display, some instances of SonarQube have thousands of users. The new behaviour of the user list improves the user experience on such systems.
Side note: If an unexpected error occurred during startup you indeed might have to reindex the database once. To do this stop SonarQube, make a backup of everything, remove the data/es directory and start SonarQube again.
Related
I am completely new to using Elasticsearch and I am having problems running scripts on my windows 10 PC ever since running the command to generate accounts for ELK stack with passwords.
elasticsearch-setup-passwords auto
Running to random errors like writing access disabled to 'missing authentication credentials for REST request' , I just want to completely reset all these to the state it was after the first time I installed elasticsearch. Because I have tried uninstalling elasticsearch but it does not remove the account information that were generated. Please help me out.
Please note that I am using the Basic version.
I have DB2 11.1 installed on Windows 7. 'db2admin' user account was created to access this. I was able to create, select and perform all necessary actions. Everything was working properly, until one fine morning it started giving me this error while connecting to database.
SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001
I performed below things:
Reset the password
Verified if the user account is disabled on Windows.
Account is not disbaled
Verified if the account is part of appropriate groups and ensured it has all necessary privileges on Windows
User groups
Deleted the 'db2admin' account and created a new one.
None of them worked and am still unable to figure out the reason for this error.
Is the error misleading? If so, any suggestions to verify logs or anything to figure out the root cause?
Any help in resolving this is highly appreciated
I'm trying to publish locally against a SQLExpress instance to test the publish capability of VS Database Project and i"m running into an error where it's trying to create a user that already exists within the database. The user creation isn't being wrapped within an IF EXISTS and I'm not seeing any type of setting to control or enforce this.
Specifically, it's throwing:
Creating [xyz\abc46518]...
(208,1): SQL72014: .Net SqlClient Data Provider: Msg 15063, Level 16, State 1, Line 1 The login already has an account under a different user name.
(208,0): SQL72045: Script execution error. The executed script:
CREATE USER [xyz\abc46518] FOR LOGIN [xyz\abc46518];
While other parts of the script have 'IF EXISTS' and 'IF NOT EXISTS', this part of the script does not.
I'd like to be able to have this as a part of the script to control the users within the database. Should someone choose to grant access and it's not in source, it's going away when we deploy.
I started using database projects, they are great, except for the user permissions.
I only have dba permissions to our databases, whereas handling logins is at the server level.
So when creating the database projects I'd get the following code generated:
CREATE USER [UserName] for login
Which when I went to build the project would error.
Well I wanted the users, but didn't want the hassle of having to keep track of post deployment scripts, largely because they ruined my lovely TFS structure.
My solution, which is a bit of a hack, instead of creating a user, I just created a role with the same name:
CREATE ROLE [UserName]
AUTHORIZATION [dbo];
Now I can assign permissions to the user for my objects (I know all access should be through roles, but its not my database, so I'm happy to hack a fix)
We never deploy roles ourselves, so it doesn't matter to us devs that its a role or a user.
I created a user in weblogic by following the below steps:
1. clicked on security realams present on left side panel.
2. clicked on myrealam
3. clicked on user and groups
4. clicked on new
5. Provided user name and password
The user created successfully. However when I am starting the server by deleting the log,cache, tmp and data folder. The created user is getting deleted automatically.
From my first level analysis I found its due to the deletion of data folder.
I want to create a permanent user for security validation.
Can anyone Please help me to create a permanent user.
Regards
Asutosh Kar
I got the answer to solve my above issues.
There are 2 ways to solve the above issue:
1. Export the LDAP files from the security realms to a directory present in the server and delete the data directory and restart the server. After restart of the server again import the LDAP files.
2. Modify the DefaultAuthenticatorInit.ldift present under the domain security directory to add the user and group details. After that delete the data directory and restart the server.
Regards
Asutosh Kar
I tried following and it works
Login to weblogic console.
Navigate to domain.
Under domain , security tab > Embedded LDAP
Select Master First and then restart servers.
The users created after restart will remain in the system
The DC is set up to lock out after three failures however this particular member that has some different applications is getting locked out after one failure. Any ideas what could be causing this to happen?
This mostly happens when the user has logged on to another device with their credentials then changed their password. Now the other device/service is trying to log on/run with the old cached credentials. This has happened to me a few times before because I have tasks running on multiple servers under my credentials and after changing my password (90 days) I forgot to change them on the other machines. Try having the user log out or shut off all devices they have used then reset their credentials. That worked for me. Microsoft also has tools to figure out where these credentials are being used.