Il 12 maggio 2017 18:14:24 CEST, sasha gesta ha scritto:
>How can I check it? In connector or in resource?
>
I reproduced your settings in my env and I'm able to pull users from ApacheDS
to Syncope.
I think there is an user in ApacheDS that have one of the mapped
Hi,
so I'm trying to log in to syncope via webservices, /syncope/rest/accessToken,
but i get 404 error;
also the accessTokens tab doesn't show when I navigate on my browser to /syncope
any ideias on whats going on?
Thanks,
Hugo Cerdeira.
Hi,
you can check it by going configurations > types > schemas and theres a
field for multivalue,
or by sending a get request to /syncope/rest/schema/{type}/{key}
sasha gesta wrote
> How can I check it? In connector or in resource?
>
> On Fri, May 12, 2017 at 6:55 PM, Marco Di Sabatino Di
How can I check it? In connector or in resource?
On Fri, May 12, 2017 at 6:55 PM, Marco Di Sabatino Di Diodoro <
marco.disabat...@tirasa.net> wrote:
>
>
> Il 12/05/2017 17:10, sasha gesta ha scritto:
>
> *Connector* :
>
> host : ldap1.example.org
> tcp port : 10389
> principal :
This mapping item is wrong:
{
"key": "d721e6e2-c9dd-4966-a1e6-e2c9dd0966ef",
"intAttrName": "password",
"extAttrName": "password",
"connObjectKey": false,
"password": false,
"mandatoryCondition": "true",
"purpose": "PROPAGATION",
"propagationJEXLTransformer": null,
"pullJEXLTransformer":
Here's the mapping:
"mapping": {
"connObjectLink": null,
"connObjectKeyItem": {
"key": "aea740be-78ea-4784-a740-be78ead784b3",
"intAttrName": "username",
"extAttrName": "userLoginId",
"connObjectKey": true,
"password": false,
"mandatoryCondition": "true",
"purpose": "PROPAGATION",
On 12/05/2017 11:49, HugoCerdeira wrote:
yes, it does include the password: internal attribute=password; external
attribute=password; mandatory = true
Please provide more details about this mapping item: just read it via
REST and paste the JSON content (or a screenshot from Admin Console).
yes, it does include the password: internal attribute=password; external
attribute=password; mandatory = true
ilgrosso wrote
> On 12/05/2017 11:31, Hugo Cerdeira wrote:
>> Hi,
>>
>> I'm trying to propagate a User when creating it via rest services of
>> the syncope-core, I'm able to create him
On 12/05/2017 11:31, Hugo Cerdeira wrote:
Hi,
I'm trying to propagate a User when creating it via rest services of
the syncope-core, I'm able to create him successfully but I get this
propagation error:
"propagationStatuses": [
{
"beforeObj": null,
"afterObj": null,
Hi,
I'm trying to propagate a User when creating it via rest services of the
syncope-core, I'm able to create him successfully but I get this propagation
error:
"propagationStatuses": [
{
"beforeObj": null,
"afterObj": null,
"resource": "ofbizUsersPropagation",
Hi Sasha,
Il 12/05/2017 09:29, sasha gesta ha scritto:
Hello,
I tried to connect Syncope 2.0.3 to ApacheDS 2.0.0-M23, but it ended
with unsuccessful bind to ldap server :
Connection failure: ConnectorException
[OperationNotSupportedException: [LDAP: error code 53 -
UNWILLING_TO_PERFORM:
VM with syncope
OS : Ubuntu 16.04.2 LTS
Container : Apache Tomcat/8.0.32
Syncope 2.0.3 JAZZ
VM with ApacheDS
OS : Ubuntu 16.04.2 LTS
apacheds-2.0.0-M23
On Fri, May 12, 2017 at 10:44 AM, Marco Di Sabatino Di Diodoro <
marco.disabat...@tirasa.net> wrote:
> Hi Sasha,
>
> Il 12/05/2017 09:29,
Hi Sasha,
Il 12/05/2017 09:29, sasha gesta ha scritto:
Hello,
I tried to connect Syncope 2.0.3 to ApacheDS 2.0.0-M23, but it ended
with unsuccessful bind to ldap server :
Connection failure: ConnectorException
[OperationNotSupportedException: [LDAP: error code 53 -
UNWILLING_TO_PERFORM:
Hello,
I tried to connect Syncope 2.0.3 to ApacheDS 2.0.0-M23, but it ended with
unsuccessful bind to ldap server :
Connection failure: ConnectorException [OperationNotSupportedException:
[LDAP: error code 53 - UNWILLING_TO_PERFORM: Bind failed: Cannot Bind for
Dn uid=admin,ou=system]]
14 matches
Mail list logo