Password Reset Token Generation Not Working After Upgrading to 2.0.4

When I make a REST call to the User Self confirmPasswordReset API for a users I am getting a JPA persistence error. It seems that it is not able to save the User object because of the token value, see value below. I just recently upgrade to 2.0.4, prior to the upgrade this was working. Anyone

Re: Pull users from LDAP

Sasha, I'm curious, were you able to resolve this issue? I am facing a similar issue myself. For me the first time I run a pull task it works fine be then fails because I have a mapping issue (not really related to this) but then after that every time I try to run the pull task again I get this

Re: AW: Password Reset Token Generation Not Working After Upgrading to 2.0.4

I have created a bug for this. SYNCOPE-1175: Password Reset Token Generation Not Working After Upgrading to 2.0.4 https://issues.apache.org/jira/browse/SYNCOPE-1175 -- View this message in context:

Re: Pull users from LDAP

Francesco, I am using the the AD connector (net.tirasa.connid.bundles.ad) v1.3.2 to connect to Microsoft Active Directory. Below is the configuration. *Connector*

Re: Cannot get Must Change Password to sync with ApacheDS pwdReset Attribute

I am using Syncope 2.0.3 and am doing a Maven war overly. -- View this message in context: http://syncope-user.1051894.n5.nabble.com/Cannot-get-Must-Change-Password-to-sync-with-ApacheDS-pwdReset-Attribute-tp5709254p5709277.html Sent from the syncope-user mailing list archive at Nabble.com.

Re: Error with openJPA multithreading

Rajkumar, Were you able to solve this issue, I am facing the same error. I will see this sometimes when using the admin console at the same time someone is hitting the REST endpoints. I know the message says you can override the Multithreaded property for OpenJPA to override this but I have

Cannot get Must Change Password to sync with ApacheDS pwdReset Attribute

Hi All, I am using the Syncope 2.0.3 with ApacheDS 2.0.0-M23 for identity store. In ApacheDS I have Must Change Password enabled for the password policy. When a new user is created the pwdReset flag is true. How can I get Syncope to change the flag to False? Changing the Must Change Password

Re: Error with openJPA multithreading

Is anyone able to provide any insight into this issue as I am getting this quite often during testing both from the syncope console and from direct API calls. -- View this message in context: http://syncope-user.1051894.n5.nabble.com/Error-with-openJPA-multithreading-tp5709137p5709267.html

Re: Cannot get Must Change Password to sync with ApacheDS pwdReset Attribute

Francesco, Thanks for your reply. I have followed the steps you described but am not getting the same result as you. If in ApacheDS password policy section I have Allow Must Change flagged then when I try to create a new user the sync with ApacheDS fails, it complains that there are 2 values

Re: Cannot get Must Change Password to sync with ApacheDS pwdReset Attribute

Francesco, pwdRest is part of the pwdpolicy schema (OID: 1.3.6.1.4.1.42.2.27.8.1.22) I am creating a user using the inetOrgPerson class. If you are using Apache Directory Studio to look at the objects this attribute will not show by default, you will need to include optional attributes to get it

Re: Cannot get Must Change Password to sync with ApacheDS pwdReset Attribute

No thoughts as to why changes to mustChangePassword are not triggering a prorogation task? Are there any configure values that I may have missed while setting up the connector or schema object that will impact this? -- View this message in context:

Re: Request Password Request API Not Working After Upgrade from 2.0.4 to 2.0.6

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

Re: Request Password Request API Not Working After Upgrade from 2.0.4 to 2.0.6

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

Re: Request Password Request API Not Working After Upgrade from 2.0.4 to 2.0.6

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

Re: Request Password Request API Not Working After Upgrade from 2.0.4 to 2.0.6

Francesco, I have reverted all of my previous changes and replaced with your latest set and it appears to be working fine now. Thanks for your support. Thanks, Justin Isenhour -- Sent from: http://syncope-user.1051894.n5.nabble.com/

Reset Password Not Resetting Must Change Password Flag

I am currently running v2.0.6 and have recently noticed that if we toggle on the Must Change Password flag then go through the Password Reset process we are seeing the password changed and is syncing with the ldap connector but I do not see the Must Change Password flag getting reset back to

Re: Reset Password Not Resetting Must Change Password Flag

I checked the core-connid logs, it looks like at the time that the update is trigger the value is still set to true. Internal Attribute: mustChangePassword External Attribute: pwdReset JXEL: mustChangePassword == 1 17:56:42.080 DEBUG Enter: search(ObjectClass: __ACCOUNT__, EQUALS:

Re: Reset Password Not Resetting Must Change Password Flag

Hey Francesco, I took the code you committed, added it to my local 2.0.6 version and tested it out. I now see that the Must Change Password flag does get set back to false after the password reset process is completed, however, this change isn't getting sync'd back to the ldap that I have linked

Re: LDAP Connection Timeout connecting to ApacheDS

The root cause of this issue has been identified and resolved. The root cause was a performance issue with ApacheDS. We allow for the changing of UIDs (which maps to the users email address) so our match is not based on UID but syncopes user key which was added as a custom schema object in

LDAP Connection Timeout connecting to ApacheDS

Hey, I am running Syncope 2.0.6 in production and have a propagation task setup to sync to ApacheDS. Over the past few weeks we have seen sporadic issues where calls to ApacheDS are failing due to connection timeout. It appears sporadic at first then after some time (few hours) all calls begin

AfterHandlingJob fails in clustered environment

Hello, We are currently running v2.0.6 in a clustered environment and have noticed that some notifications are not being generated when we bulk create users related to a migration effort from a legacy system. The error we are getting in the logs is listed below. Based on the code that I have

Default Quartz Misfire Threshold

Hello, The current configuration of Quartz defined in provisioningContext.xml under syncope-core-provisioning-java project has the misfire threshold set to 600 (100 minutes). The default value for Quartz is 1 minute, is there a specific reason that this value was changed to 100 minutes? The

Must Change Password Sync with ApacheDS

Hey All, We are working on upgrading from Syncope 2.0.6 to 2.0.14 and have run into an issue. We have a custom UI that we use to allow admin to create users within specific realms. The user will then get the Account Created email template and will be taken to our custom branded UI to set their