Hey,
I am not able to proceed. Please help.
Regards,
Harsh sharma
On Tue, Oct 28, 2014 at 1:31 PM, Harsh Sharma
wrote:
> Also I am encountering with one more error:
>
> If I am creating user in active directory, I am able to see that in
> syncope, but I am not able to login to syncope with the
Also I am encountering with one more error:
If I am creating user in active directory, I am able to see that in
syncope, but I am not able to login to syncope with the password I had set
in Active directory. I am only able to login by syncope if I change
password in syncope of that created user.
Il 27/10/2014 02:10, Harsh Sharma ha scritto:
Hey Fabio,
Whenever I am removing value for membership property and saving it ,
it automatically sets to same user principal value when I open it
again. Should I assign it manually to some other value ?
Hi Harsh, you can remove a valu by following
Hey Fabio,
Whenever I am removing value for membership property and saving it , it
automatically sets to same user principal value when I open it again.
Should I assign it manually to some other value ?
Regards,
Harsh Sharma
On Sat, Oct 25, 2014 at 11:42 AM, Fabio Martelli
wrote:
> Hi Harsh, y
Hi Harsh, your are right, sorry. Password mapping is correct.
It seems that the problem occurs during 'group administrator' assignment.
Taking a look at your connector conf I see that you set user principal as
membership. Please review your conf removing value for memberships property.
Regards,
Hi Harsh, your are right, sorry. Password mapping is correct.
It seems that the problem occurs during 'group administrator' assignment.
Taking a look at your connector conf I see that you set user principal as
membership. Please review your conf removing value for memberships property.
Regards,
Hey guys,
Please help. I have been stuck on it for a long time.
Regards,
Harsh Sharma
On Fri, Oct 24, 2014 at 11:00 PM, Harsh Sharma
wrote:
> Hey,
>
> I think as the password is in encrypted form , that why the password field
> is like that :
>
> Attribute: {Name=__PASSWORD__,
> Value=[org.i
Hey,
I think as the password is in encrypted form , that why the password field
is like that :
Attribute: {Name=__PASSWORD__,
Value=[org.identityconnectors.common.security.GuardedString@f0b270c2]}
Yes I mapped the password mapping and also selected the password checkbox.
attaching user mapping
Il 24/10/2014 12:59, Harsh Sharma ha scritto:
Hey,
Please find the attached core-connid.log and the snapshot of the error
message when I created a user named "google".
Hi Harsh, it seems you are missing password.
Not unicodePwd but __PASSWORD__ attribute. Did you mapped password
attribute by
Hey,
Please find the attached core-connid.log and the snapshot of the error
message when I created a user named "google".
Also in core-rest.log I am getting this warning message
"09:54:38.989 WARN
org.apache.syncope.core.persistence.validation.entity.EntityValidationListener
- Bean validation err
Hi Harsh, your configuration seems good, btw provided info is not enough
to make a complete diagnosis.
Can you send core-connid.log file?
Regards,
F.
Il 22/10/2014 23:48, Harsh Sharma ha scritto:
Hey Francesco,
Now when I am creating a user in Syncope it is reflecting in Active
directory, bu
On 19/10/2014 14:42, Harsh Sharma wrote:
Hello,
I am connecting apache syncope to active directory. I am able to
retrieve Users from Active directory. I can change password and other
attributes of the retrieved users, But I am not able to create user in
active directory. I mean whenever I am cre
Hello,
I am connecting apache syncope to active directory. I am able to
retrieve Users from Active directory. I can change password and other
attributes of the retrieved users, But I am not able to create user in
active directory. I mean whenever I am creating user in apache syncope
and saving it,
13 matches
Mail list logo
