i am using obiee 12c in production and Active Directory ldap server entegrated for authentication. almost all users are able to login analytics but few of these users cannot login. the following error appearing in the screen "The specified credentials could not be authenticated ". I tried to regenerate user GUIDs according to following documents. https://docs.oracle.com/middleware/1221/core/BIMIG/GUID-E2ABAAA2-FFA2-453F-9C42-4F00807B4708.htm#BIMIG-GUID-E2ABAAA2-FFA2-453F-9C42-4F00807B4708
I set the BI component's log level to Finest and enable debug security option. I examined acces log, bi server diagnostic log and sawlog files, but i can not see any log that contains any failure information about the failed LDAP user.
Could you help me about this problem, thanks.
a) That link is invalid since GUIDs do not exist anymore. The documentation shouldn't include that step anymore.
b) Logging the BI components won't show you anything. You need to up up the OPSS logging.
Related
We have noticed ~15k failed login attempts a day on one of our admin-accounts in the domain.
The source server is found and the event type is "Network", the source is a DC that has not been touched (except WinUpd) for years so a virus seems unlikely but of course possible.
Is there a way to trace exactly what the failed attempts point at? We have recently changed FSMO roles between two other DCs in the domain, maybe that has something to do with it?
You can check the login failed attemps based in audit logon events local computer policy.
use the keyboard shortcut Windows Key + R and type:gpedit.msc in the Run line and hit Enter.
In Group Policy Editor, navigate to Windows Settings >> Security Settings >> Local Policy >> Audit Policy.
Then double click on Audit Logon Events.
From there, check the boxes to audit failed audit attempts and click OK.
There you go! Now you’ll be able to see the complete logon activities (failed l) for your Windows computer.
Please refer this one as well based on event id you can know exactly what the failed attempts point at. : https://social.technet.microsoft.com/Forums/en-US/f49cd4d6-a7d5-4213-8482-72d1d5306dab/windows-server-2012-r2-help-finding-failed-logon-attempts-source?forum=winserversecurity
Reference: https://www.groovypost.com/howto/pin-windows-8-start-screen-programs-desktop/
I am following this tutorial, when I came to the point of restarting the BI server to reflect the newly added repository, then my trial to restart failed !
logs attached as appearing in the log viewer
edit : I navigated to the nqserver log file and found the following :
Oracle BI Server startup failed.[nQSError: 13042] Repository password is wrong.
Ok can't really be more clear than your error message. The RPD password is wrong. Either re-upload with the correct password or change the currently stored password in the credential store
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.
When I tried to connect to the navigator web administration, I receive a message "The desktop can not be opened" and It require defining a desktop ID.
http://imgur.com/JNKelPy
How to fix this problem or define a desktop ID?
I can't remember if after an installation default desktop is admin or if you have to set it manually. Is your URL with ?desktop=admin at the end working (https://ecm.filenet.com:9443/navigator/?desktop=admin)? If it does, create a desktop and set it as default. If it doesn't, you should take a look at the WAS log (SystemOut.log) to see what the error is.
After successful deployment of IBM Content Navigator, the admin desktop is automatically created. It is considered the default desktop until another is created with a valid repository. If you have issues, you should put in the full admin console address:
http://www.ICNADDRESS.com:9080/navigator/?desktop=admin
The desktop selection code at the end (?desktop=) can be used to specifically go to any desktop in the configuration, but the code treats the admin console address shown above as "special" for authentication and processes it slightly differently. I've had normal desktop configurations (especially after upgrades from 2.0.1 & 2.0.2) have issues for administrative users.
IBM Content Navigator uses DB tables for it's configuration data. You can find the desktop related info in a table named CONFIGMGMT including admin desktop.
There are server possibilities for the error that you are getting
CONFIGMGMT table has corrupted data regarding admin desktop.
CONFIGMGMT table has been deleted.
The DB table is accessed by Content Navigator via data source created in your application server and the connection to the underlying database is not made due to authentication issues(very common due to password change policies).
I have the following problem: i need to log in a log file somewhere the time at which an incorrect password is tried in an attempt to login in windows 7.
I seached the internet but was not able to find that.
Does anyone know how this is done?
All system login/authentication attempts are logged in the Security Audit Log within the Windows Event Viewer by default. These logs are written by the Local Security Authority Subsystem Service (LSASS.exe). It is possible to analyze these events and filter out the exact information that you want.