You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by Nicola Baiocco <ni...@intesys.it> on 2015/01/26 16:25:57 UTC

User and Role Data binder problem

Hi,

we have some problem during update propagations to external resource of users and roles in Syncope 1.2.1.
In our case, the external resource has a derived attribute configured as account id.

During the propagation task it seems that syncope performs a getRemoteObject operation (in AbstractPropagationTaskExecutor)  passing username/rolename attribute instead of the designed account id attribute (internal attribute specified in user/role mapping configuration).
This behavior it seems an issue and we have resolved with attached patch.
Could you confirm that?
Otherwise if we have a misunderstanding could you explain what is the business logic behind this routine (UserDataBinder update and RoleDataBinder update).

Thanks in advance,
Best regards.

[http://www.intesys.it/firme/logo_intesys.jpg]
Nicola Baiocco | Software Developer
Intesys - Via Roveggia 122 A - 37136 Verona
Tel. 045 503663 | Fax 045 503604
nicola.baiocco@intesys.it
www.intesys.it<http://www.intesys.it>
[Great Place to Work]<http://www.intesys.it/Partecipazione-dei-dipendenti/>   [Sito a impatto zero] <http://www.intesys.it/Sostenibilita-Ambientale/>
Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa è vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore è pregato di inoltrarlo al mittente e di cancellare questa e-mail.
This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message.

R: User and Role Data binder problem

Posted by Nicola Baiocco <ni...@intesys.it>.
Hi Francesco,

Your version works well for us, we will open a new issue.

Thanks a lot.

Nicola Baiocco | Software Developer

Intesys - Via Roveggia 122 A  - 37136 Verona
Tel. 045 503663 | Fax 045 503604
nicola.baiocco@intesys.it
www.intesys.it

Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa ? vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore ? pregato di inoltrarlo al mittente e di cancellare questa e-mail.

This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. 

-----Messaggio originale-----
Da: Nicola Baiocco [mailto:nicola.baiocco@intesys.it] 
Inviato: mercoledì 28 gennaio 2015 09:52
A: dev@syncope.apache.org
Oggetto: R: User and Role Data binder problem

Ok,

we will test your code and we'll let you know as soon as possible.

Thanks.

Nicola Baiocco | Software Developer

Intesys - Via Roveggia 122 A  - 37136 Verona Tel. 045 503663 | Fax 045 503604 nicola.baiocco@intesys.it www.intesys.it

Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa ? vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore ? pregato di inoltrarlo al mittente e di cancellare questa e-mail.

This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. 
-----Messaggio originale-----
Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
Inviato: mercoledì 28 gennaio 2015 09:02
A: dev@syncope.apache.org
Oggetto: Re: User and Role Data binder problem

Hi,
with your original patch, when added to Syncope sources (not to your project sources), I got the following failures during integration tests
execution:

updateAsRoleOwner(org.apache.syncope.core.rest.RoleTestITCase) Time
elapsed: 0.148 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: NotFound [AccountId mapping for ROLE 7 on resource 'ws-target-resource-nopropagation']
         at
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy42.update(Unknown Source)
         at
org.apache.syncope.core.rest.RoleTestITCase.updateAsRoleOwner(RoleTestITCase.java:341)

updateWitApproval(org.apache.syncope.core.rest.UserSelfTestITCase) Time
elapsed: 0.173 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: Workflow [Error while evaluating expression: #{update.execute(execution.processInstanceId)}]
         at
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy41.submitForm(Unknown Source)
         at
org.apache.syncope.core.rest.UserSelfTestITCase.updateWitApproval(UserSelfTestITCase.java:210)

I have reworked your patch at https://paste.apache.org/2zJK and failures are gone: can you try my patch and let me know if it still solves your problem?
If so, can you please open an issue on JIRA with description of your problem? Thanks.

Regards.

On 27/01/2015 14:24, Nicola Baiocco wrote:
> We currently use this patch in our core overlay.
>
> we've  left line 106 commented because we don't understand its meaning of this one, this type of operation should be performed after this routine (as happens for role process) otherwise will lost the old values.
>
> All the other comments are our missing, sorry.
>
> Hope this will clarify a little bit.
>
> -----Messaggio originale-----
> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
> Inviato: martedì 27 gennaio 2015 14:11 A:dev@syncope.apache.org
> Oggetto: Re: User and Role Data binder problem
>
> On 27/01/2015 14:07, Nicola Baiocco wrote:
>> Here, our solution patch:
>>
>> http://apaste.info/Fqa
> Thanks: have you tried to apply such patch to Syncope sources and to check that the build runs successfully?
>
> Minor note: I see comments in the patch, you should remove them.
>
> Regards.
>
>> -----Messaggio originale-----
>> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
>> Inviato: martedì 27 gennaio 2015 13:31 A:dev@syncope.apache.org
>> Oggetto: Re: User and Role Data binder problem
>>
>> On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
>>> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>>> Hi,
>>>>
>>>> we have some problem during update propagations to external 
>>>> resource of users and roles in Syncope 1.2.1.
>>>>
>>>> In our case, the external resource has a derived attribute 
>>>> configured as account id.
>>>>
>>>> During the propagation task it seems that syncope performs a 
>>>> getRemoteObject operation (in AbstractPropagationTaskExecutor) 
>>>> passing username/rolename attribute instead of the designed account 
>>>> id attribute (internal attribute specified in user/role mapping 
>>>> configuration).
>>>>
>>>> This behavior it seems an issue and we have resolved with attached 
>>>> patch.
>>>>
>>>> Could you confirm that?
>>>>
>>>> Otherwise if we have a misunderstanding could you explain what is 
>>>> the business logic behind this routine (UserDataBinder update and 
>>>> RoleDataBinder update).
>>>>
>>> Hi Nicola,
>>> sorry I cannot see your patch - probably it's safer to paste it to 
>>> https://paste.apache.org/
>> Sorry,http://apaste.info/  should work (the one above is for ASF committers).
>>
>>> You should also provide some more information about your resource 
>>> mapping.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/


R: User and Role Data binder problem

Posted by Nicola Baiocco <ni...@intesys.it>.
Ok,

we will test your code and we'll let you know as soon as possible.

Thanks.

Nicola Baiocco | Software Developer

Intesys - Via Roveggia 122 A  - 37136 Verona
Tel. 045 503663 | Fax 045 503604
nicola.baiocco@intesys.it
www.intesys.it

Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa ? vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore ? pregato di inoltrarlo al mittente e di cancellare questa e-mail.

This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. 
-----Messaggio originale-----
Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org] 
Inviato: mercoledì 28 gennaio 2015 09:02
A: dev@syncope.apache.org
Oggetto: Re: User and Role Data binder problem

Hi,
with your original patch, when added to Syncope sources (not to your project sources), I got the following failures during integration tests
execution:

updateAsRoleOwner(org.apache.syncope.core.rest.RoleTestITCase) Time
elapsed: 0.148 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: NotFound [AccountId mapping for ROLE 7 on resource 'ws-target-resource-nopropagation']
         at
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy42.update(Unknown Source)
         at
org.apache.syncope.core.rest.RoleTestITCase.updateAsRoleOwner(RoleTestITCase.java:341)

updateWitApproval(org.apache.syncope.core.rest.UserSelfTestITCase) Time
elapsed: 0.173 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: Workflow [Error while evaluating expression: #{update.execute(execution.processInstanceId)}]
         at
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy41.submitForm(Unknown Source)
         at
org.apache.syncope.core.rest.UserSelfTestITCase.updateWitApproval(UserSelfTestITCase.java:210)

I have reworked your patch at https://paste.apache.org/2zJK and failures are gone: can you try my patch and let me know if it still solves your problem?
If so, can you please open an issue on JIRA with description of your problem? Thanks.

Regards.

On 27/01/2015 14:24, Nicola Baiocco wrote:
> We currently use this patch in our core overlay.
>
> we've  left line 106 commented because we don't understand its meaning of this one, this type of operation should be performed after this routine (as happens for role process) otherwise will lost the old values.
>
> All the other comments are our missing, sorry.
>
> Hope this will clarify a little bit.
>
> -----Messaggio originale-----
> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
> Inviato: martedì 27 gennaio 2015 14:11 A:dev@syncope.apache.org
> Oggetto: Re: User and Role Data binder problem
>
> On 27/01/2015 14:07, Nicola Baiocco wrote:
>> Here, our solution patch:
>>
>> http://apaste.info/Fqa
> Thanks: have you tried to apply such patch to Syncope sources and to check that the build runs successfully?
>
> Minor note: I see comments in the patch, you should remove them.
>
> Regards.
>
>> -----Messaggio originale-----
>> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
>> Inviato: martedì 27 gennaio 2015 13:31 A:dev@syncope.apache.org
>> Oggetto: Re: User and Role Data binder problem
>>
>> On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
>>> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>>> Hi,
>>>>
>>>> we have some problem during update propagations to external 
>>>> resource of users and roles in Syncope 1.2.1.
>>>>
>>>> In our case, the external resource has a derived attribute 
>>>> configured as account id.
>>>>
>>>> During the propagation task it seems that syncope performs a 
>>>> getRemoteObject operation (in AbstractPropagationTaskExecutor) 
>>>> passing username/rolename attribute instead of the designed account 
>>>> id attribute (internal attribute specified in user/role mapping 
>>>> configuration).
>>>>
>>>> This behavior it seems an issue and we have resolved with attached 
>>>> patch.
>>>>
>>>> Could you confirm that?
>>>>
>>>> Otherwise if we have a misunderstanding could you explain what is 
>>>> the business logic behind this routine (UserDataBinder update and 
>>>> RoleDataBinder update).
>>>>
>>> Hi Nicola,
>>> sorry I cannot see your patch - probably it's safer to paste it to 
>>> https://paste.apache.org/
>> Sorry,http://apaste.info/  should work (the one above is for ASF committers).
>>
>>> You should also provide some more information about your resource 
>>> mapping.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/


Re: User and Role Data binder problem

Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi,
with your original patch, when added to Syncope sources (not to your 
project sources), I got the following failures during integration tests 
execution:

updateAsRoleOwner(org.apache.syncope.core.rest.RoleTestITCase) Time 
elapsed: 0.148 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: NotFound [AccountId 
mapping for ROLE 7 on resource 'ws-target-resource-nopropagation']
         at 
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy42.update(Unknown Source)
         at 
org.apache.syncope.core.rest.RoleTestITCase.updateAsRoleOwner(RoleTestITCase.java:341)

updateWitApproval(org.apache.syncope.core.rest.UserSelfTestITCase) Time 
elapsed: 0.173 sec  <<< ERROR!
org.apache.syncope.common.SyncopeClientException: Workflow [Error while 
evaluating expression: #{update.execute(execution.processInstanceId)}]
         at 
org.apache.syncope.common.SyncopeClientException.build(SyncopeClientException.java:37)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.checkSyncopeClientCompositeException(RestClientExceptionMapper.java:99)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:56)
         at 
org.apache.syncope.client.rest.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:39)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
         at 
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
         at com.sun.proxy.$Proxy41.submitForm(Unknown Source)
         at 
org.apache.syncope.core.rest.UserSelfTestITCase.updateWitApproval(UserSelfTestITCase.java:210)

I have reworked your patch at https://paste.apache.org/2zJK and failures 
are gone: can you try my patch and let me know if it still solves your 
problem?
If so, can you please open an issue on JIRA with description of your 
problem? Thanks.

Regards.

On 27/01/2015 14:24, Nicola Baiocco wrote:
> We currently use this patch in our core overlay.
>
> we've  left line 106 commented because we don't understand its meaning of this one, this type of operation should be performed after this routine (as happens for role process) otherwise will lost the old values.
>
> All the other comments are our missing, sorry.
>
> Hope this will clarify a little bit.
>
> -----Messaggio originale-----
> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
> Inviato: martedì 27 gennaio 2015 14:11
> A:dev@syncope.apache.org
> Oggetto: Re: User and Role Data binder problem
>
> On 27/01/2015 14:07, Nicola Baiocco wrote:
>> Here, our solution patch:
>>
>> http://apaste.info/Fqa
> Thanks: have you tried to apply such patch to Syncope sources and to check that the build runs successfully?
>
> Minor note: I see comments in the patch, you should remove them.
>
> Regards.
>
>> -----Messaggio originale-----
>> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
>> Inviato: martedì 27 gennaio 2015 13:31
>> A:dev@syncope.apache.org
>> Oggetto: Re: User and Role Data binder problem
>>
>> On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
>>> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>>> Hi,
>>>>
>>>> we have some problem during update propagations to external resource
>>>> of users and roles in Syncope 1.2.1.
>>>>
>>>> In our case, the external resource has a derived attribute
>>>> configured as account id.
>>>>
>>>> During the propagation task it seems that syncope performs a
>>>> getRemoteObject operation (in AbstractPropagationTaskExecutor)
>>>> passing username/rolename attribute instead of the designed account
>>>> id attribute (internal attribute specified in user/role mapping
>>>> configuration).
>>>>
>>>> This behavior it seems an issue and we have resolved with attached
>>>> patch.
>>>>
>>>> Could you confirm that?
>>>>
>>>> Otherwise if we have a misunderstanding could you explain what is
>>>> the business logic behind this routine (UserDataBinder update and
>>>> RoleDataBinder update).
>>>>
>>> Hi Nicola,
>>> sorry I cannot see your patch - probably it's safer to paste it to
>>> https://paste.apache.org/
>> Sorry,http://apaste.info/  should work (the one above is for ASF committers).
>>
>>> You should also provide some more information about your resource
>>> mapping.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/


R: User and Role Data binder problem

Posted by Nicola Baiocco <ni...@intesys.it>.
We currently use this patch in our core overlay.

we've  left line 106 commented because we don't understand its meaning of this one, this type of operation should be performed after this routine (as happens for role process) otherwise will lost the old values.

All the other comments are our missing, sorry.

Hope this will clarify a little bit.


Nicola Baiocco | Software Developer

Intesys - Via Roveggia 122 A  - 37136 Verona
Tel. 045 503663 | Fax 045 503604
nicola.baiocco@intesys.it
www.intesys.it

Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa ? vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore ? pregato di inoltrarlo al mittente e di cancellare questa e-mail.

This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. 

-----Messaggio originale-----
Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org] 
Inviato: martedì 27 gennaio 2015 14:11
A: dev@syncope.apache.org
Oggetto: Re: User and Role Data binder problem

On 27/01/2015 14:07, Nicola Baiocco wrote:
> Here, our solution patch:
>
> http://apaste.info/Fqa

Thanks: have you tried to apply such patch to Syncope sources and to check that the build runs successfully?

Minor note: I see comments in the patch, you should remove them.

Regards.

> -----Messaggio originale-----
> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
> Inviato: martedì 27 gennaio 2015 13:31
> A: dev@syncope.apache.org
> Oggetto: Re: User and Role Data binder problem
>
> On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
>> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>> Hi,
>>>
>>> we have some problem during update propagations to external resource 
>>> of users and roles in Syncope 1.2.1.
>>>
>>> In our case, the external resource has a derived attribute 
>>> configured as account id.
>>>
>>> During the propagation task it seems that syncope performs a 
>>> getRemoteObject operation (in AbstractPropagationTaskExecutor) 
>>> passing username/rolename attribute instead of the designed account 
>>> id attribute (internal attribute specified in user/role mapping 
>>> configuration).
>>>
>>> This behavior it seems an issue and we have resolved with attached 
>>> patch.
>>>
>>> Could you confirm that?
>>>
>>> Otherwise if we have a misunderstanding could you explain what is 
>>> the business logic behind this routine (UserDataBinder update and 
>>> RoleDataBinder update).
>>>
>> Hi Nicola,
>> sorry I cannot see your patch - probably it's safer to paste it to 
>> https://paste.apache.org/
> Sorry, http://apaste.info/ should work (the one above is for ASF committers).
>
>> You should also provide some more information about your resource 
>> mapping.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/


Re: User and Role Data binder problem

Posted by Francesco Chicchiriccò <il...@apache.org>.
On 27/01/2015 14:07, Nicola Baiocco wrote:
> Here, our solution patch:
>
> http://apaste.info/Fqa

Thanks: have you tried to apply such patch to Syncope sources and to 
check that the build runs successfully?

Minor note: I see comments in the patch, you should remove them.

Regards.

> -----Messaggio originale-----
> Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
> Inviato: martedì 27 gennaio 2015 13:31
> A: dev@syncope.apache.org
> Oggetto: Re: User and Role Data binder problem
>
> On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
>> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>> Hi,
>>>
>>> we have some problem during update propagations to external resource
>>> of users and roles in Syncope 1.2.1.
>>>
>>> In our case, the external resource has a derived attribute configured
>>> as account id.
>>>
>>> During the propagation task it seems that syncope performs a
>>> getRemoteObject operation (in AbstractPropagationTaskExecutor)
>>> passing username/rolename attribute instead of the designed account
>>> id attribute (internal attribute specified in user/role mapping
>>> configuration).
>>>
>>> This behavior it seems an issue and we have resolved with attached
>>> patch.
>>>
>>> Could you confirm that?
>>>
>>> Otherwise if we have a misunderstanding could you explain what is the
>>> business logic behind this routine (UserDataBinder update and
>>> RoleDataBinder update).
>>>
>> Hi Nicola,
>> sorry I cannot see your patch - probably it's safer to paste it to
>> https://paste.apache.org/
> Sorry, http://apaste.info/ should work (the one above is for ASF committers).
>
>> You should also provide some more information about your resource
>> mapping.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/


R: User and Role Data binder problem

Posted by Nicola Baiocco <ni...@intesys.it>.
Here, our solution patch:

http://apaste.info/Fqa 

Best regards.

Nicola Baiocco | Software Developer

Intesys - Via Roveggia 122 A  - 37136 Verona
Tel. 045 503663 | Fax 045 503604
nicola.baiocco@intesys.it
www.intesys.it

Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa ? vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore ? pregato di inoltrarlo al mittente e di cancellare questa e-mail.

This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. 
-----Messaggio originale-----
Da: Francesco Chicchiriccò [mailto:ilgrosso@apache.org] 
Inviato: martedì 27 gennaio 2015 13:31
A: dev@syncope.apache.org
Oggetto: Re: User and Role Data binder problem

On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>
>> Hi,
>>
>> we have some problem during update propagations to external resource 
>> of users and roles in Syncope 1.2.1.
>>
>> In our case, the external resource has a derived attribute configured 
>> as account id.
>>
>> During the propagation task it seems that syncope performs a 
>> getRemoteObject operation (in AbstractPropagationTaskExecutor)  
>> passing username/rolename attribute instead of the designed account 
>> id attribute (internal attribute specified in user/role mapping 
>> configuration).
>>
>> This behavior it seems an issue and we have resolved with attached 
>> patch.
>>
>> Could you confirm that?
>>
>> Otherwise if we have a misunderstanding could you explain what is the 
>> business logic behind this routine (UserDataBinder update and 
>> RoleDataBinder update).
>>
>
> Hi Nicola,
> sorry I cannot see your patch - probably it's safer to paste it to 
> https://paste.apache.org/

Sorry, http://apaste.info/ should work (the one above is for ASF committers).

> You should also provide some more information about your resource 
> mapping.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/


Re: User and Role Data binder problem

Posted by Francesco Chicchiriccò <il...@apache.org>.
On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
> On 26/01/2015 16:25, Nicola Baiocco wrote:
>>
>> Hi,
>>
>> we have some problem during update propagations to external resource 
>> of users and roles in Syncope 1.2.1.
>>
>> In our case, the external resource has a derived attribute configured 
>> as account id.
>>
>> During the propagation task it seems that syncope performs a 
>> getRemoteObject operation (in AbstractPropagationTaskExecutor) 
>>  passing username/rolename attribute instead of the designed account 
>> id attribute (internal attribute specified in user/role mapping 
>> configuration).
>>
>> This behavior it seems an issue and we have resolved with attached 
>> patch.
>>
>> Could you confirm that?
>>
>> Otherwise if we have a misunderstanding could you explain what is the 
>> business logic behind this routine (UserDataBinder update and 
>> RoleDataBinder update).
>>
>
> Hi Nicola,
> sorry I cannot see your patch - probably it's safer to paste it to 
> https://paste.apache.org/

Sorry, http://apaste.info/ should work (the one above is for ASF 
committers).

> You should also provide some more information about your resource 
> mapping.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/


Re: User and Role Data binder problem

Posted by Francesco Chicchiriccò <il...@apache.org>.
On 26/01/2015 16:25, Nicola Baiocco wrote:
>
> Hi,
>
> we have some problem during update propagations to external resource 
> of users and roles in Syncope 1.2.1.
>
> In our case, the external resource has a derived attribute configured 
> as account id.
>
> During the propagation task it seems that syncope performs a 
> getRemoteObject operation (in AbstractPropagationTaskExecutor) 
>  passing username/rolename attribute instead of the designed account 
> id attribute (internal attribute specified in user/role mapping 
> configuration).
>
> This behavior it seems an issue and we have resolved with attached patch.
>
> Could you confirm that?
>
> Otherwise if we have a misunderstanding could you explain what is the 
> business logic behind this routine (UserDataBinder update and 
> RoleDataBinder update).
>

Hi Nicola,
sorry I cannot see your patch - probably it's safer to paste it to 
https://paste.apache.org/
You should also provide some more information about your resource mapping.

Regards.

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/