I have a Bolt Authentication issue that I don't know how to solve. I restored a backup from my online provider to my local machine. I can launch the browser and run "CALL db.schema" and the query returns. But when i try to just select a sample set of data I'm seeing this in the logs and the query never returns.
2018-06-25 14:39:23.778+0000 ERROR Unexpected error detected in bolt session 'ace2d3fffe92e75d-0005b714-00000004-4c1990029792d052-f94315d8'. The client is unauthorized due to authentication failure.
org.neo4j.bolt.v1.runtime.BoltConnectionFatality: The client is unauthorized due to authentication failure.
at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:742)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:728)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.access$500(BoltStateMachine.java:62)
at org.neo4j.bolt.v1.runtime.BoltStateMachine$State$1.init(BoltStateMachine.java:435)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.init(BoltStateMachine.java:145)
at org.neo4j.bolt.v1.messaging.BoltMessageRouter.lambda$onInit$0(BoltMessageRouter.java:70)
at org.neo4j.bolt.runtime.MetricsReportingBoltConnection.lambda$enqueue$0(MetricsReportingBoltConnection.java:69)
at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:195)
at org.neo4j.bolt.runtime.MetricsReportingBoltConnection.processNextBatch(MetricsReportingBoltConnection.java:87)
at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:143)
at org.neo4j.bolt.runtime.ExecutorBoltScheduler.executeBatch(ExecutorBoltScheduler.java:170)
at org.neo4j.bolt.runtime.ExecutorBoltScheduler.lambda$scheduleBatchOrHandleError$2(ExecutorBoltScheduler.java:153)
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
In my config file I can turn off security: dbms.security.auth_enabled=false and things will work. But I'd like to understand why/how I'm getting this error so I don't have to do that. In the administration tab of the desktop I've tried changing the password and it says it's successful but the error still remains?
Restoring to an identical version resolves issue. So good knowledge to have, back ups must be restored to identical versions. Or at least v3.3.5 restored to 3.4 will present this issue.
Related
I am extremely new to UiPath. I have inherited a project from an experienced UiPath developer. I am trying to find the username and password he uses to login to a specific app. Because the project is not working when executing in the development environment, it is possible the password has expired. I am on the machine he used to develop the project, but logged in under my name. I have found the process that does the "Get Credential". I am using a message box to show the username at this point. When I run the process The "Get Credential" activity returns the error "you are not authenticated Error Code:0" I have researched the error and found several answers as to why it is happening, but not what to do to either fix my problem or get around the problem. The UiPath.systems.Activites version used is 21.4.1. I am aware of the concept of the CredentialStores, but can't seem to find the one used for this project. Where would I find the name of the credential store used? How do I find the username? I need to test the change I made for a user request.
I am going to close this question as I have determined the correct password for what I needed to do. I have no need to get into the credential stores for a password.
Credential stores and password were not the actual issue with the error I was receiving. The error "Loading asset PreAuth_Citrix_FolderName failed:
You are not authenticated! Error code: 0" by referencing the word authenticated, I assumed it had to do with passwords. As I did more research I found the issue to be the new security certificate installed on our web server. While orchestrator recognized the new cert, the Identity Server was not updated with the new thumbprint. I found the information I need at this link https://forum.uipath.com/t/get-asset-you-are-not-authenticated-error-code-0/343910. Once I updated the Identity Server thumbprint, I no longer received the error and my jobs ran. (not successful, but at least they ran past this error!)
Recently changed the password for our weblogic server by following these guides 1 and 2. I skipped the nodemanager password reset part for guide 2. But when I restarted the server encountered multiple issues see below. Can you please advise on how to fix these errors.
Weblogic and Oracle Linux version
Weblogic 12c
Linux 3.10.0-229.el7.x86_64
A MultiException has 8 exceptions. They are:
1. weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.rmi.cluster.RemoteBinderFactoryService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.rmi.cluster.RemoteBinderFactoryService
7. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cluster.ClusterServiceActivator errors were found
8. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cluster.ClusterServiceActivator
Update
I wasn't able to pinpoint the exact error as to why it's giving me all these messages. But am almost 90% sure it's related when I modified boot.properties.
I was able to fix it by restarting the deleting some folders related to weblogic restart like ldap, sessions. Also deleted boot.properties and modified the username and password again which is similar to the original credentials I entered. Because I suspect that weblogic is not able to match the new boot.properties credentials with the configured credentials in weblogic.
I faced the similar issue. Then followed below steps and it worked:
Added weblogic username and password in startWeblogic.[sh|cmd]
Clear the ldap and store directory under domain_home/servers//data
Cleared the tmp directory parallel to data directory (as above)
Restarted the managed server
I have an application that connects to an SQL Server Compact Edition 3.5 database. The application will randomly fail, throwing a SqlCeException with the message "bad hash." What is causing this exception and how can I prevent it? I can't find any information on google that might explain what's going on. The problem seems to be fixable with a reboot, but I would like to know more about what causes it and how to prevent it.
System.Data.SqlServerCe.SqlCeException: Bad Hash.
at System.Data.SqlServerCe.SqlCeConnection.ProcessResults(Int32 hr)
at System.Data.SqlServerCe.SqlCeConnection.Open(Boolean silent)
at System.Data.SqlServerCe.SqlCeConnection.Open()
Sometimes, mostly at nighttime, our SSL certificates just stop working.
The error accompanying this fault is:
A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10001.
To solve this at the moment, we just change the SSL binding of the faulting website to a different site, save it and switch it back. That way, the certificate is picked up again and works (magic).
The question is: How can we prevent this from happening? Every time this happens (now twice in the last 6 months), the sites are down.
An article I found resolved the issue: https://techcommunity.microsoft.com/t5/iis-support-blog/error-hresult-0x80070520-when-adding-ssl-binding-in-iis/ba-p/377281
FYI, we have checked all three options.
If this error should come up again, I will post it here.
I too have had this problem. My server service was working fine for hours if in use but if left for 45 minutes without a call, it would get this error. So there was some sort of timeout or other expiry occurring. I wrote a utility to monitor my service, and of course that kept it alive. So I adjusted times, and found the period that let it fail. I re-examined all the web references I'd used, and found that re-reading the article at paulstovell.com it mentioned the PersistKeySet property. Changing my code which prepares the certificate to include this, so it is now like:
X509Certificate2 cert = new X509Certificate2(file, password, X509KeyStorageFlags.PersistKeySet | X509KeyStorageFlags.MachineKeySet | X509KeyStorageFlags.Exportable);
has fixed the problem, and the certificate no longer expires or times out with the 0x8009030d error. And of course this makes sense, as the error is about there being no key, and persisting it is what is required.
http://paulstovell.com/blog/x509certificate2
by editing the permission on C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys I have resolve the same issue thanks
We are using a custom database data store in OpenAM. This store authenticates user against our Oracle database.
Now, there are many possible causes why that authentication might fail. The account could be locked in Oracle or the password might be expired.
The datastore catches the SQLException, but how do I propagate the cause to the OpenAM UI?
I can throw a AuthLoginException from authenticate(), but on its way to the AMLoginContext, it gets wrapped and AMLoginContext kind of ignores error codes of AuthLoginExceptionS anyway. Meaning: AMLoginContext doesn't read the error code from the exception but tries to determine the error code itself, and usually it just puts AMAuthErrorCode.AUTH_LOGIN_FAILED into the login state.
How do I get the UI to show the cause of the login problem?
As Bernhard says, that is not recommended. However, from your data store you could obtain a Debug instance (com.sun.identity.shared.debug.Debug) and you can log exceptions, and they will appear in [AM_INSTALL_DIR]/openam/debug.
edit: You can find examples of doing so throughout the OpenAM source code.