SonarQube 5.6 with LDAP 2.1.0.507 plugin - active-directory

I am running SonarQube 5.6 in a docker machine with the following settings.
LDAP configuration
General Configuration sonar.security.realm=LDAP
sonar.security.savePassword=false
sonar.forceAuthentication=true ldap.url=ldap://ad.yyy.xxx.com:389 ldap.bindDN=CN=Administrator,CN=Users,DC=yyy,DC=xxx,DC=com
ldap.bindPassword=xxxx#ddddd
User Configuration
ldap.user.baseDn=CN=Users,DC=yyy,DC=xxx,DC=com ldap.user.baseDn=DC=xxx,DC=com
ldap.user.request=(&(objectClass=user)(sAMAccountName={login})) ldap.user.request=(sAMAccountName={0})
ldap.user.request=(&(objectClass=inetOrgPerson)(uid={login}))
ldap.user.realNameAttribute=cn ldap.user.realNameAttribute=displayName ldap.user.emailAttribute=mail
sonar.log.level=DEBUG
While connecting AD user I am getting the following error.
2017.05.19 21:14:43 DEBUG web[o.s.p.l.LdapUsersProvider] [LDAP: error code 1 - 000004DC: LdapErr: DSID-0C090752, comment: In order to
perform this operation a successful bind m ust be completed on the
connection., data 0, v2580] javax.naming.NamingException: [LDAP:
error code 1 - 000004DC: LdapErr: DSID-0C090752, comment: In order to
perform this operation a successful bind must be completed on the con
nection., data 0, v2580]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3175) ~[na:1.8.0_91]
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081)
~[na:1.8.0_91]
2017.05.19 21:14:43 DEBUG web[o.s.p.l.LdapUsersProvider] User ajeesh not found in
2017.05.19 21:14:43 ERROR web[rails] Error from external users provider: exception Java::OrgSonarPluginsLdap::LdapException: Unable
to retrieve details for user ajeesh in

Related

com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user ''. ClientConnectionId:

I'm trying to connect to microsoft sql server using 8.2 version of jar.
It works fine when I'm using the same username, password in DBeaver. I'm not using any additional options in the connection string of DBeaver. I'm using the type SQLServer Authentication. It gets connected in DBeaver but I'm not able to open a connection via Scala repl.
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver")
val props=new java.util.Properties
props.put("user","")
props.put("password","")
// URL : jdbc:sqlserver://host:port // No additional options like in DBeaver
DriverManager.getConnection("url",props)
Error:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'USERNAME'. ClientConnectionId:CONNECTIONID
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:283)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:129)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5173)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3810)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:94)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3754)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7225)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3053)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2562)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2216)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2067)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1204)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:825)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
... 47 elided

ODI Start agent fail

When I try to start odi agent with this command:
C:\ORACLE_HOME\user_projects\domains\ODIDOMAIN\bin>agent -NAME=OracleDIAgent1 -PORT=20910
This error is shown:
ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
the full text is:
2020-11-04 07:17:58.676 NOTIFICATION New data source: [DEV_ODI_REPO/*******#jdbc:oracle:thin:#//10.1.5.66:1521/ORCL66]
2020-11-04 07:18:04.599 NOTIFICATION ODI-1128 Agent OracleDIAgent1 is starting. Container: STANDALONE. Agent Version: 12.2.1. Port: 20910. JMX Port: 21910.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Allowing : 127.0.0.1,10.1.5.66,127.0.0.1
2020-11-04 07:18:10.088 WARNING odi.core.security.SecurityManager.loadAuthenticationMode found the authMode:mUsingLDAPAuthentication: false,mUsingIDCSAuthentication:false,indExternalAuth:null.
2020-11-04 07:18:10.420 ERROR ODI-1131 Agent OracleDIAgent1 encountered an error: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository. Caused by: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.420 WARNING ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.435 WARNING unavailable
2020-11-04 07:18:10.435 WARNING Failed startup of context o.o.#17125ea9{/oraclediagent,file:/C:/ORACLE_HOME/user_projects/domains/ODIDOMAIN/system_components/ODI/OracleDIAgent1/work/webapp/,STARTING}{file:/C:/ORACLE_HOME/odi/agent/lib/./oraclediagent.war}
2020-11-04 07:18:10.435 WARNING FAILED o.o.#17125ea9{/oraclediagent,file:/C:/ORACLE_HOME/user_projects/domains/ODIDOMAIN/system_components/ODI/OracleDIAgent1/work/webapp/,UNAVAILABLE}{file:/C:/ORACLE_HOME/odi/agent/lib/./oraclediagent.war}: javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.471 WARNING FAILED org.eclipse.jetty.server.Server#77bca6d6: javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.472 ERROR ODI-1443 Error while starting agent : ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.503 ERROR ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.503 ERROR javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
The ODI version is 12 and node manager and weblogic is starting correctly.
As the error message states, the ODI username or password that was provided when configuring the agent is incorrect.
To reconfigure the agent and set the correct credentials on Windows :
execute config.cmd in C:\ORACLE_HOME\oracle_common\common\bin
click next on all the steps except the ODI Server Configuration page where you can type the password
start the agent
More info in Oracle Support Doc ID 2386816.1
Its not the problem with SUPERVISOR credentials. if you have multiple Agents in various servers you may face this issue. only one agent may fail out of n.
Copy the ODI_MASTER_ENCODED_PASS value to the expected location within the odiparams.sh file on the system where the agent is not starting.
The odiparams.sh file can be found in:
$ODI_HOME\oracledi\agent\bin

Getting error while connecting to Cassandra in mule

details : Mule 3.8, CassendraDB downloaded from mulesoft exchange, Cassandra version 3.x, port no : 9042.
The Following error occurs when I test connection in cassandra connector configuration.
Error : org.mule.api.ConnectionException: Read a negative frame size (-2147483648)! at com.mulesoft.mule.cassandradb.CassandraDBConnector.connect(CassandraDBConnector.java:101) at com.mulesoft.mule.cassandradb.connectivity.CassandraDBConnectorConnectionFactory.makeObject(CassandraDBConnectorConnectionFactory.java:52) at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) at com.mulesoft.mule.cassandradb.connectivity.CassandraDBConnectorConnectionManager.acquireConnection(CassandraDBConnectorConnectionManager.java:269) at com.mulesoft.mule.cassandradb.connectivity.CassandraDBConnectorConnectionManager.test(CassandraDBConnectorConnectionManager.java:351) at org.mule.tooling.metadata.api.utils.ConnectionTester.internalTestConnection(ConnectionTester.java:88) at org.mule.tooling.metadata.api.utils.ConnectionTester.testConnectionFor(ConnectionTester.java:113) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1$1.call(TestConnectorConnectionFromMuleConfigAction.java:68) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1$1.call(TestConnectorConnectionFromMuleConfigAction.java:1) at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:25) at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:17) at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:37) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1.run(TestConnectorConnectionFromMuleConfigAction.java:65) at java.lang.Thread.run(Unknown Source) Caused by: org.mule.api.ConnectionException: Read a negative frame size (-2147483648)! at com.mulesoft.mule.cassandradb.CassandraDBUtils.getClient(CassandraDBUtils.java:90) at com.mulesoft.mule.cassandradb.CassandraDBConnector.connect(CassandraDBConnector.java:94) ... 13 more
How can I resolve this error ?
There are a number of potential config changes that you can try.
Check the following in the cassandra.yaml
authenticator: org.apache.cassandra.auth.PasswordAuthenticator
rpc_address: 0.0.0.0
... and consequently ...
broadcast_rpc_address: NOT 0.0.0.0 eg 1.2.3.4
start_rpc: to true
This is because the MuleSoft cassandraDB connector uses apache thrift and not a native connection. You will also need to set the host and Port in the connection settings in studio to be 0.0.0.0 and 9160 respectively. Trst with a blank username/password pair and it should show a correct connection.

Error: Test Connection Failed for MC_Ten. Failed to Connect to the End Point : Reason Unknown

I'm trying to create a connection "Salesforce Marketing Cloud (Cloud Computing)" in Informatica Cloud as shown in the picture
But it gives me the error in question
File fuelsdk-test.properties I entered:
endpoint= https : // www . exacttargetapis . com
authEndpoint= https : // auth . exacttargetapis . com
soapEndpoint= https : // webservice . s7 . exacttarget . com / Service . asmx
username=********
password=*********
clientId=*************************
clientSecret=**********************
Can you tell me how to fix the error?
Below some log (tomcat.log) if can be useful for any response:
2015-11-30 22:17:43,936 ERROR [com.informatica.saas.toolkit.metadataRead.resources.PluginsResource] - Exception Thrown in Operation: connect
com.informatica.cloud.api.adapter.connection.ConnectionFailedException: Failed to Connect to the End Point : Reason Unknown
at com.informatica.saas.toolkit.metadataRead.Dao.PluginDao.connect(PluginDao.java:248)
at com.informatica.saas.toolkit.metadataRead.resources.PluginsResource.connect(PluginsResource.java:234)
at sun.reflect.GeneratedMethodAccessor349.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215)
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
I am working for Informatica,
Error message thrown when testing the connection is either one of the connection attributes or context of the plugin fails to do connection which results the code to throw the exception error message.
"Failed to Connect to the End Point : Reason Unknown"
There is no specific information supplied in the exception to find the reason of failure.
Please post your question in informatica community for more quicker response on informatica products.
https://network.informatica.com/welcome

LDAP - Active Directory Error Codes - Receive Error 52e instead of 773

We are attempting to login to Active Directory using Spring-LDAP-1.3.1-RELEASE version, with a user who has an account option set User must change password at next logon.
The problem is that a 52e (invalid credentials) is returned, instead of the 773 error code (user must reset password). The exception is throw as is from the AD server and printed out in the org.springframework.ldap.AuthenticationException class. The exact exception is:
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1
Has anyone had a similar issue where a 52e is returned from Active Directory, when it should be returning a 773?
A list of the error codes can be found here:
http://www-01.ibm.com/support/docview.wss?uid=swg21290631

Resources