Re: Cannot access attributes in custom pull action

Hello, That makes sense that Syncope will only return attributes that are mapped despite what Search Script returns. I think I have that but I must be missing it. Attached is an image of my mapping. One thing I see in

Re: Cannot access attributes in custom pull action

On 17/03/20 17:34, roccom wrote: > Francesco, when I call delta.getObject() I get this: MyPullActions3 - > delta.getObject(): {Uid=Attribute: > {Name=__UID__, Value=[834f03a5-f5c5-42d5-ac61-21757444e929]}, > ObjectClass=ObjectClass: __ACCOUNT__,

Re: Cannot access attributes in custom pull action

Francesco, when I call delta.getObject() I get this: MyPullActions3 - delta.getObject(): {Uid=Attribute: {Name=__UID__, Value=[834f03a5-f5c5-42d5-ac61-21757444e929]}, ObjectClass=ObjectClass: __ACCOUNT__, Attributes=[Attribute: {Name=username,

Re: Cannot access attributes in custom pull action

On 16/03/20 21:56, roccom wrote: > I have a custom pull action groovy script running when I run my pull action. > My understanding is that the search script fires and builds a conn object > with the attributes I have mapped. Next the custom pull action fires. I can > see this in core.log with lots