Francesco Chicchiriccò created SYNCOPE-1125:
-----------------------------------------------
Summary: Password on external resource not updated via Enduser
Key: SYNCOPE-1125
URL: https://issues.apache.org/jira/browse/SYNCOPE-1125
Project: Syncope
Issue Type: Bug
Components: enduser
Affects Versions: 2.0.3
Reporter: Francesco Chicchiriccò
Fix For: 2.0.4, 2.1.0
As [reported in mailing
list|https://lists.apache.org/thread.html/b0d3c5f584f107065b988400f4865f7b9e4bb951ae201da9fd99e908@%3Cuser.syncope.apache.org%3E],
the issue can be replicated with standalone distribution / embedded mode:
# from Admin Console, create user {{[email protected]}}, set {{Password123}}
as password value and assign `resource-ldap`
# user is successfully created and propagated
# binding via LDAP works fine with the password set above:
{code}
ldapsearch -h localhost -p 1389 -D "[email protected],ou=People,o=isp" -x
-w Password123 -b "[email protected],ou=People,o=isp"
{code}
# from Admin Console, update the user above by setting the password to
{{Password124}}
# binding via LDAP works fine with updated password:
{code}
ldapsearch -h localhost -p 1389 -D "[email protected],ou=People,o=isp" -x
-w Password124 -b "[email protected],ou=People,o=isp"
{code}
# from Enduser UI, login as {{[email protected]}} / {{Password124}} and set
the password to {{Password125}}
At this point:
* {{Password125}} is set on Syncope
* {{Password124}} is still set on LDAP
* a {{DELETE}} propagation task was created as consequence of Enduser UI
password change
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
