Essential Debug loggers for WSO2 Identity Server
When you are working with WSO2 products, you have to enable debug logs to investigate issues. Its better to enable debug logs only for particular module that you need to investigate. It reduce debug writing time and unnecessary debug reading time.So you can easily understand the root cause when you are reading the console.I'm going to discuss about debug lines one by one.
You have to add debug line to [WSO2_HOME]\repository\conf\log4j.properties file, all debug lines are displayed in the console and write to the wso2carbon.log file.
To enable loggers for user core.This is helpful to investigate user related issues.
To enable debug logs for identity module. This debug log will be helpful to investigate identity related issues.
When you are working with WSO2 products, you have to enable debug logs to investigate issues. Its better to enable debug logs only for particular module that you need to investigate. It reduce debug writing time and unnecessary debug reading time.So you can easily understand the root cause when you are reading the console.I'm going to discuss about debug lines one by one.
You have to add debug line to [WSO2_HOME]\repository\conf\log4j.properties file, all debug lines are displayed in the console and write to the wso2carbon.log file.
To enable loggers for user core.This is helpful to investigate user related issues.
log4j.logger.org.wso2.carbon.user.core=DEBUG
To enable debug logs for identity module. This debug log will be helpful to investigate identity related issues.
log4j.logger.org.wso2.carbon.identity=DEBUG
If you need to investigate saml assertion or assertion related issue, you can enable debug logs for saml sso module.
log4j.logger.org.wso2.carbon.identity.sso.saml=DEBUG
To enable synaps wire logs. (You cannot enable wire logs with Identity Server. But you can enable wire logs with other WSO2 products like ESB, APIM,)
log4j.logger.org.apache.synapse.transport.http.headers=DEBUG
log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
To enable logs for SCIM
log4j.logger.org.wso2.carbon.user.core=DEBUG
log4j.logger.org.wso2.carbon.identity.scim.provider=DEBUG
log4j.logger.org.wso2.carbon.identity.scim.common.listener.SCIMUserOperationListener=DEBUG
If you want to enable debug logs for authentication framework, You can investigate authentication session related issues.
log4j.logger.org.wso2.carbon.identity.application.authentication.framework=DEBUG
To enable synapse wire logs
log4j.logger.org.apache.synapse.transport.http.headers=DEBUG
log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
Issues are related to LDAP, you can enabled below log
log4j.logger.org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager=DEBUG
I will explain other debug logs one by one
#log4j.logger.org.wso2.carbon.identity.application=DEBUG
#log4j.logger.org.wso2.carbon.identity.mgt=DEBUG
#log4j.logger.org.wso2.carbon.identity.oauth2=DEBUG
#log4j.logger.org.wso2.carbon.identity.scim=DEBUG
#log4j.logger.org.wso2.carbon.identity.mgt=DEBUG
#log4j.logger.org.wso2.carbon.idp.mgt=DEBUG
#log4j.logger.org.wso2.carbon.identity.provisioning=DEBUG
#log4j.logger.org.wso2.carbon.identity.user.account.association=DEBUG
#log4j.logger.org.wso2.carbon.identity.user.profile.mgt=DEBUG
#log4j.logger.org.wso2.carbon.security=DEBUG
#log4j.logger.org.wso2.carbon.identity.sso.agent=DEBUG
#log4j.logger.org.wso2.carbon.identity.core=DEBUG
Comments
Post a Comment