Could we connect to ldap server without providing any value in securityPrincipal and securityCredentials parameters in init in esb wso2?
If not, what exactly should be the value we need to provide for securityPrincipal and securityCredentials parameters in init operation for connecting to ldap server in esb wso2.
I am getting below error while calling searchEntry operation after init operation in esb wso2.
{
"error": {
"errorMessage": "simple bind failed: ldapxxx.xxx.com:389",
"errorCode": 7000002
}
}
I got it working by setting below parameters.
"securityPrincipal":"",
"securityCredentials":"",
"secureConnection":"true",
"disableSSLCertificateChecking":"true",
Related
I am following the steps from this guide to connect to the on-prime database using spark.
https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/data-sources/apache-spark-sql-connector
tried this code:
servername = "XXXXX"
dbname = "poplesdb"
url = servername + ";" + "databaseName=" + dbname + ";"
dbtable = "Test"
user = "test\user"
password = mssparkutils.credentials.getSecret('xxxx','xxxxxxx')
I got this error:
Py4JJavaError: An error occurred while calling z:mssparkutils.credentials.getSecret.
: com.twitter.finagle.NoBrokersAvailableException: No hosts are available for XXXX.vault.azure.net:443, Dtab.base=[], Dtab.local=[]. Remote Info: Not Available
I am trying this connection test since days. please anyone help me?
Here my screen shots of linked service . I need to connect the source inside retail database
Py4JJavaError: An error occurred while calling
z:mssparkutils.credentials.getSecret. :
com.twitter.finagle.NoBrokersAvailableException: No hosts are
available for XXXX.vault.azure.net:443, Dtab.base=[], Dtab.local=[].
Remote Info: Not Available
Given error indicates that a request failed because no servers were available. This typically occurs under one of the following conditions:
The cluster is actually down. No servers are available. - A service discovery failure. This can be due to a number of causes, such as the client being constructed with an invalid cluster destination name or a failure in the service discovery system (e.g. DNS).
A good way to diagnose NoBrokersAvailableExceptions is to reach out to the owners of the service to which the client is attempting to connect and verify that the service is operational. If so, then investigate the service discovery mechanism that the client is using.
I'm building a client server to connect with Hyperledger Fabric network using fabric-go-sdk. To use a custom logging system, I get an FabricSDK object using fabsdk.New() then inject it to a Gateway object using gateway.WithSDK function. Check the code below:
ccpPath := getPath("connection-profile.json", staticPath)
sdk, err := fabsdk.New(config.FromFile(ccpPath),
fabsdk.WithLoggerPkg(&FabSDKLoggerProvider{}), // using my custom logging system
)
if err != nil {
return nil, errors.Wrap(err, "failed to create a new fabsdk")
}
gw, err := gateway.Connect(
gateway.WithSDK(sdk),
gateway.WithIdentity(wallet, "admin"),
)
if err != nil {
return nil, errors.Wrap(err, "failed to connect the network via a fabric gateway")
}
When I run a test, I get an error:
Failed to submit: error registering for TxStatus event: could not create client conn: could not connect to peer0.test.bpl:7051: dialing connection on target [peer0.test.bpl:7051]: connection is in TRANSIENT_FAILURE
The test that I ran is a test to send a transaction using the Gateway object and its Submit method.
When I defined a Gateway object without FabricSDK, it works fine. That is, if I use the code below, the test passes well. However, in this case, I cannot use my custom logging system. (I just want to disable Fabric SDK's logging system.)
ccpPath := getPath("connection-profile.json", staticPath)
gw, err := gateway.Connect(
gateway.WithConfig(config.FromFile(ccpPath)),
gateway.WithIdentity(wallet, "admin"),
)
if err != nil {
return nil, errors.Wrap(err, "failed to connect the network via a fabric gateway")
}
According to my investigation, difference between FabricSDK objects initialized by fabsdk.New() and gateway.Connect(gateway.WithConfig()) is that the FabricSDK object that is created by gateway.Connect(gateway.WithConfig()) has the option fabsdk.WithMSPPkg(gw.mspfactory) but the other does not. I try to give the same option to my fabsdk.New() code, I could not find how to do it.
So, my question is:
How can I deal with "TRANSIENT_FAILURE" error, or
How can I disable the Fabric SDK's default logging system?
Thanks.
I just had exactly the same two questions while writing a little sample CLI to get chaincode metadata
How can I deal with "TRANSIENT_FAILURE" error
In my case, the dialing connection on target [peer0.org1.example.com:7051]: connection is in TRANSIENT_FAILURE error was because I was using the Fabric test network docker environment but I had not set the DISCOVERY_AS_LOCALHOST environment variable. DISCOVERY_AS_LOCALHOST determines whether IP addresses found during service discovery are translated from the docker network to the local host, which is described in the Connection Options documentation for developing applications.
How can I disable the Fabric SDK's default logging system?
I still wanted to see error messages but I was able to change the logging level to get rid of unwanted info messages using logging.SetLevel("", logging.ERROR)
The ccmetadata sample is on GitHub if that's any help
I'm trying to use the Docusign API for an application that I'm running locally and I see the following error:
"message":"Uncaught Error when executing a Single
Cause: com.docusign.esign.client.ApiException: Error while
requesting server, received a non successful HTTP code 400 with response Body:
'{"errorCode":"HTTPS_REQUIRED_FOR_CONNECT_LISTENER",
"message":"HTTPS required for Connect listener communication."}'
Description: com.docusign.esign.client.ApiException: Error while
requesting server, received a non successful HTTP code 400 with response Body:
'{"errorCode":"HTTPS_REQUIRED_FOR_CONNECT_LISTENER",
"message":"HTTPS required for Connect listener communication."}
I am behind a company proxy but I have been able to use the API in the past and create envelopes without an issue so I'm not sure how to address this. Any help would be greatly appreciated.
This change is discussed in the Jan release notes.
Connect can only be used with https listeners (customers' servers).
And note that the server must use a certificate that chains to a root cert in the Microsoft standard root cert list. (Self-signed certs won't work.) You can use a free cert from LetsEncrypt or a $15 cert from a reputable CA.
I'm sorry that this update caught you by surprise.
Getting error now, it was working fine before:
Fatal error: Uncaught DocuSign\eSign\Client\ApiException: Error while requesting server, received a non successful HTTP code [400] with response Body: O:8:"stdClass":2:{s:9:"errorCode";s:35:"HTTPS_REQUIRED_FOR_CONNECT_LISTENER";s:7:"message";s:50:"HTTPS required for Connect listener communication.";}
Upon using the DataFacotry Connector to Snowflake, I consistently get the error message below. Does anyone have any idea how to fix this?
I am using an Azure-managed Integration Runtime.
ERROR [HY000] [Microsoft][Snowflake] (4) REST request for URL
https://xxxxxxx.east-us-2.azure.snowflakecomputing.com.snowflakecomputing.com:443/session/v1/login-request?requestId=2fb149b1-5f57-47ad-a471-8a8db718336c&request_guid=25dcec4f-f680-4f18-b018-363084843708&databaseName=DEMO_DB&warehouse=COMPUTE_WH failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer
certificate or SSH remote key was not OK'.
ERROR [HY000] [Microsoft][Snowflake] (4) REST request for URL
https://xxxxxxx.east-us-2.azure.snowflakecomputing.com.snowflakecomputing.com:443/session/v1/login-request?requestId=2fb149b1-5f57-47ad-a471-8a8db718336c&request_guid=25dcec4f-f680-4f18-b018-363084843708&databaseName=DEMO_DB&warehouse=COMPUTE_WH failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer
certificate or SSH remote key was not OK'.
Activity ID: 376547c0-6604-454d-b881-544cb6e7811a.
Probably not a good idea, from a security perspective, to leave your account id visible like this.
Anyway, the issue is probably that you have mis-configured your connection as snowflake.com is repeated: ...snowflakecomputing.com.snowflakecomputing.com
We're facing an issue where Jetty SPNEGO gives an NPE inside SpnegoLoginService.login()
The gssContext.getSrcName() call returns null.
The SPN is: HTTP/machine.dd.aa.net#EE.AA.NET
Must there be a special setup in the KRB5.INI file when dd.aa.net != EE.AA.NET ?
The only clue i found with Google is this warning message from some online source code:
if (gssContext.isEstablished()) {
if (gssContext.getSrcName() == null) {
log.warn("GSS Context accepted, but no context initiator recognized. Check your kerberos configuration and reverse DNS lookup configuration");
return false;
}
Our client-setup is
Internet-explorer browser, setup for negotiate/spnego
login using Windows SmartCard
Our server-setup is
Java 8u45
Jetty 9
using org.eclipse.jetty.security.SpnegoLoginService
We used java kinit on the server to validate against the keytab and also against the DC. which went ok. Also the reverse DNS zones are working.
is there a possibility that the 'service request token' generated by the client browser (logged in with smartcard) doesn't supply the context initiator / client principle name ?
Thanks
The nullpointer was gone when we went from Java 1.8u45 to Java 1.8u60
Turns out the server side didn't check all tickets provided by the client, so didn't find the correct one.
Below the bug entry:
[JDK-8078439] SPNEGO auth fails if client proposes MS krb5 OID