Configuration of the add-on
...
- Do step 1 described above (replace the old JAR with the new one);
- Do step 8 described above (generate Google API key);
- Do step 9-12 described above (enter the key, and check whether the directory works).
- Change logging level for google api as desribed in Konwn problems section
Logging
Anchor | ||||
---|---|---|---|---|
|
Crowd logging can be changed as desribed here
All logs from this add-on and libraries it uses reside in the file
All logs from this add-on and libraries it uses reside in the file
atlassian-crowd.log
. By default INFO
log level is enabled, sometimes when there's a problem with the plugin it's too little to find the reason and you have to to increase log level of some logger, or when some logger produces too much data, you have to decrease its log level. The most interesting loggers are:...
For the exact locations of atlassian-crowd.log or log4j.properties, and for more details on logging in Crowd, see here in Crowd documentation.
Known problems
Due to a problem with Google libraries,
pl.craftware.shaded.
com.google.api.client.http.HttpTransport
logger produces too much data. If this is a problem for you, you can disable it with:log4j.logger.pl.craftware.shaded.
com.google.api.client.http.HttpTransport
=OFF
log4j.properties
.