Francesco,
I took the code changes from your commit and applied those same changes
locally but I am still getting the same error, line number references in
UserLogic.java is different due to code changes so I know it is picking up
new code. Were there any changes needed other than to
When I debug this locally I see that the UserLogic.resolveReference is
getting called, the args objects is an array that contains 2 strings. In my
test that looks like this:
[use...@place.com, charlotte]
index 0 is the username, index 1 is the answer to the security question.
The first if
After further investigation I see the issue. The code I will be referencing
is UserDataBinderImpl.java under provisioning-java project. The code we
were looking at before, UserLogic will call this classes getUserTO(string
key) method. That method in 2.0.4 had logic to get user by either key or
Oops, you're right, there is a mistake in the conditional logic, just fixed
with [1]
Please revert any other change, and make your UserLogic#resolveReference
method look like [2]
Regards.
[1]
https://github.com/apache/syncope/commit/a9cbd25f872e175fa4c4af52502f55c7b8edcdf1
[2]
Hi,
the error below is raised after all operations have been successfully
completed, as it can be derived from the stack trace element:
org.apache.syncope.core.logic.LogicInvocationHandler.around(LogicInvocationHandler.java:82)
This is why the e-mail is effectively sent, as you report.
Hi Elena,
the AD Connector [1] is an extension of the LDAP Connector [2] and
explicitly enlists it among its dependencies [3].
Hence, the AD Connector [1] is using the LDAP protocol to connect to
Active Directory instances.
I hope this clarifies.
Regards.
[1]
Hi,
I have one question: in version 2.0.7 I have noticed that you have added a
preprocess function to the default pull actions class. We would like to alter
the syncdelta in certain cases ie the user should be kept as enabled (ie.
__ENABLED__ set to true) as the user can have two different
