Il 04/04/2017 11:45, Tech ha scritto:
To make a long story short, I put a screen shot about what I mean.
Despite the graphic, also the resource RestResource was correctly
propagated, but we didn't probably handle anything that could have
made understand to Syncope that the result was
Hello,
I'm not talking about the user status, but the resource status.
When you provision a resource and you open the user profile, you will
see "Resource1(v)"
In the case there is a problem the resource will appear as
"Resource1 (x)".
I want to understand what is the information
Hi
Il 04/04/2017 09:49, Tech ha scritto:
Dear experts,
we are working with Rest and provisioning accounts to a Ws.
We are able to correctly create remotely the resource, but we are not
able to mark into the system that the propagation correctly occurred
(from the Admin Console we still see
Hi,
Ah yeah, forgot about the pull action interface. That is probably the right
place for it.
I’ll see what I can do with the office 365 thing. Basically, it is only a
system call to a server with office 365 powershell installed. Even connid cmd
could be a good start…☺
Regards,
Mikael
Dear experts,
we are working with Rest and provisioning accounts to a Ws.
We are able to correctly create remotely the resource, but we are not
able to mark into the system that the propagation correctly occurred
(from the Admin Console we still see the resource marked with (x)
instead of
Hi Mikael,
see my replies on-line.
Regards.
On 04/04/2017 09:35, Mikael Ekblom wrote:
Hi,
Ah, ok. The groovy-all.jar had to be moved into the syncope web-inf
lib directory.So now we have two options: local file bundle and
through the connid-server. Very well!
Another question by the way.
Hi,
Ah, ok. The groovy-all.jar had to be moved into the syncope web-inf lib
directory. So now we have two options: local file bundle and through the
connid-server. Very well!
Another question by the way. We have our HR-system as a cloud solution. It will
be configured as an external resource
