I already installed Cloudera manager. After that, I add Zeppelin service and I start it.
I want to launch the Zeppelin Server Web UI and to authenticate with user=admin and password=admin but I didn't succeed. Error message: "The username and password that you entered don't match."
have you any idea please to unblock the situation?
Thanks.
Related
I am trying to create a federated authentication using the Keycloak and following the steps mentioned here: Setup User Federation with Keycloak
I have been using the port 10389 instead of 389 mentioned in the document. Everything seems to be working fine until the step where I am making the connection from Keycloak to LDAP.
When I provide the Connection URL as ldap://localhost:10389 and click on the Test Connection then I get the error:
Error! Error when trying to connect to LDAP. See server.log for details
I am not sure what's wrong because when I check in the Apache Directory Studio there everything seems to be working fine for me and I am able to get all the users list etc. I am not sure why I am unable to make the connection from Keycloak to LDAP.
I tried the following things but nothing worked for me:
ldap://localhost:10389
localhost:10389
ldap://127.0.0.1:10389
ldap://localhost:389
Stopped the docker in the dashboard and started again.
After trying a lot I found the solution. Posting the answer as it can be useful to someone else in the future.
I was using the localhost and 127.0.0.1 which was not working. Finally, I checked the IP Address of my system using the terminal (for mac ipconfig) and tried that and it worked:
ldap://192.168.1.12:10389
After installing patch 10.3.6.0.200114, Weblogic console could not log in, indicating "WebLogic Server has rejected this user name or password. Please try again. " However, the service can be accessed normally
There is a bug in this PSU which prevent web app like the admin console to authenticate users. Oracle published a patch to correct this issue : SU Patch [EIL8]: 10.3.6.0.200114WLSPSU Overlay: CANNOT LOGIN TO CONSOLE, BUT CAN LOGIN TO EM WITH THE SAME USER
Download it from MOS and patch your WebLogic server installation.
I looked at the config files everything is fine, made environment variables PATH's, started and restarted the service put in the right password, searched for someone with similar problems(not found).
Every time i go to the default location via browser I get the login screen but when i put in 'root' and the password I get an error message 'Login Failed'.
When I set athenticate=false in the conf file i can access the web manager.
Anybody know how to solve this or at least what might be wrong?
During the installation, the ArangoDB Installer will ask you the password for the administrator user.
Use root as user name with your password to gain access to the database.
Open a CMD-Window in your ArangoDB installation directory.
To re-gain access to the database, stop the ArangoDB database service using
sc stop ArangoDB
after the database was stopped, invoke
.\usr\bin\arango-secure-installation
which will ask you for a new password.
After that, start the service again using:
sc start ArangoDB
I have setup an EMR 4.4 cluster with Zeppelin/Spark configured. I successfully managed to setup Zeppelin on localhost and was logged in as anonymous. I added created a user and password and continued to work with my notebook. I later started a new cluster and I am now presented with a login screen for Zeppelin which will not accept my username and password. Is there a way to flush the privileges or find out what I did enter?
Many thanks!
Added the port at the end and it allowed access.
http://127.0.0.1:8890/
We are running Glassfish 3.1.2.2 authenticating against an Active Directory realm. Authentication works correctly the vast majority of the time, but occasionally, authentication will suddenly start failing for all users, and we'll see errors like this in the server log:
[#|2014-03-19T21:37:32.331+0000|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.web.security|_ThreadID=1098;_ThreadName=Thread-2;|WEB9102: Web Login Failed: com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Failed file login for jeff.|#]
Note that the error message is failed file login. It appears as if Glassfish is occasionally reverting back to the file realm rather than the active directory realm.
When this problem happens, after a short time without any intervention on our part, authentication will suddenly start hitting Active Directory again and users will be able to login again.
Any ideas why Glassfish would occasionally revert to authentication against the file realm when we've configured it to use Active Directory? Should I delete the file realm altogether?
I finally determined the trigger for this. We had been connecting JVisualVM to our Glassfish instance to monitor performance. Everytime I connect JVisualVM (over JMX connection using Glassfish admin credentials), Glassfish immediately reverts to using the file realm instead of the LDAP realm. I have no idea why JVisualVM would cause this behavior in Glassfish, but it is consistently reproducible. The only workaround I have discovered is:
Disconnect JVisualVM.
In Glassfish admin console go to -> Configurations -> server-config -> Security
Change default realm (to anything other than LDAP realm), Save.
Change default realm back to LDAP realm, Save.
Clients should now again be able to authenticate against LDAP.