The value in 'password.cipher.algorithm' was SHA1.
We updated to AES, we changed again the password for the user and we
tried to login again to the enduser portal.
It's working, we tried to connect to AD but without success.
We realized after that the password, with a difference with the other
On 30/01/2017 12:34, Tech wrote:
When we create the user we are able to initialize the correct
password, connecting to the target system we can verify that Syncope
did its job.
If the Admin tries to reset the password from the console, or if the
user tries to change is password from the
We are associating using a manual provisioning
Here the main information:
Connector version 1.3.2
-SSL enabled
-Retrieve deleted users enabled
-Retrieve deleted groups enabled
-Trust all certs enabled
Entry object classes:
-Top
-person
-organizationalPerson
-inetOrgPerson
-user
Custom user
On 30/01/2017 15:18, Tech wrote:
Yes, I can confirm, right in this moment we are only performing manual
provisioning.
This is of course not the goal, but before moving to an automatic
provision of accounts we want the manual one working
What is your value for the 'password.cipher.algorithm'
On 30/01/2017 14:53, Tech wrote:
This is what happen when I open the Password Manager, while when I
update the password no log is generated.
This is what I suspected: you could definitely find a confirmation if
you are able to verify that the user on Active Directory has still the
password
On 30/01/2017 15:11, Tech wrote:
We are associating using a manual provisioning
Do you mean that you are only relying on a push task for provisioning to AD?
Could you confirm that you are *not* assigning the AD resource directly
to the users, neither via group membership or template?
Here
Yes, I can confirm, right in this moment we are only performing manual
provisioning.
This is of course not the goal, but before moving to an automatic
provision of accounts we want the manual one working
On 30/01/2017 15:14, Francesco Chicchiriccò wrote:
> On 30/01/2017 15:11, Tech wrote:
>>
I'm not sure about this step.
As mentioned we can already propagate changes as "email, "first name"
and "last name".
The AD user that we are using is able to change the passwords of other
AD users, create, update and delete other users.
I think that there is an additional step that was not
When we create the user we are able to initialize the correct password,
connecting to the target system we can verify that Syncope did its job.
If the Admin tries to reset the password from the console, or if the
user tries to change is password from the enduser interface, the
password is still
Hi,
Il 30/01/2017 16:45, Anas Asharat ha scritto:
Dears,
I hope my email find you well.
Am new with Syncope, I tried to install Syncope 2.0.1 with oracle
database, I face installation failure every time I tried to install
the application.
Can you help me or give document with
10 matches
Mail list logo
