Logging in Syncope scripts

[stak <AR...@GMAIL.COM>]

When logging in Syncope create/update scripts, i am unable to see the logs in
any of the log files. Is there a particular logger that needs to be enabled
for us to be able to see the log statements.

Also is there a particular reason the log in the scripts is
org.identityconnectors.common.logging and not other loggers like slf4j or
log4j or logback?

--
Sent from: http://syncope-user.1051894.n5.nabble.com/

Re: Logging in Syncope scripts

[Francesco Chicchiriccò <il...@apache.org>]

On 04/06/20 01:15, stak wrote:
> When logging in Syncope create/update scripts, i am unable to see the logs in
> any of the log files. Is there a particular logger that needs to be enabled
> for us to be able to see the log statements.
Hi,
you need to enable Audit [1] for the corresponding events, e.g.

syncope.audit.[LOGIC]:[UserLogic]:[]:[create]:[SUCCESS]
syncope.audit.[LOGIC]:[UserLogic]:[]:[update]:[SUCCESS]

After logging in as admin in the Admin Console, go to Configuration > Audit and select the two events as above.

At that point you will have the audit statements in the logs  *and* in the special SYNCOPE_AUDIT table.
Please note that, by doing so, you will also enable the "History Management" feature for users.

> Also is there a particular reason the log in the scripts is
> org.identityconnectors.common.logging and not other loggers like slf4j or
> log4j or logback?

You make quite some confusion here: slf4j is the logging API Syncope is using, log4j is the logging framework that will generate actual logging output according to its configuration, logback is one of log4j competitors (but Syncope is not using it).

Finally, org.identityconnectors.common.logging is just the name of the logger under which the logging statements you are referring to are generated.
Such statements were created in the code via slf4j and written to the core-connid.log file by log4j.

In this particular case, what you see are the statements related to the fact that a user, after creation or update in Syncope, are propagated to one or more External Resources through ConnId: please make yourself familiar with some concepts about Syncope architecture to understand more.

HTH
Regards.

[1] http://syncope.apache.org/docs/2.1/reference-guide.html#audit
[2] http://syncope.apache.org/docs/2.1/reference-guide.html#architecture

-- 
Francesco Chicchiriccò

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

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/