Apologies for the delay in sharing our latest knowledge base articles. With the hustle and bustle of the holiday season and kicking off an exciting new quarter, I experienced a slight delay in my usual posting schedule.
The updates for January and February will be coming your way soon.
This post contains all new KB (Solution) articles published in December and any articles with significant updates. The article summary provides an overview of the article’s purpose.
-
IG (All versions) won’t start with an Identity Gateway PID file already exists error
The purpose of this article is to provide assistance if IG fails to start with an “Identity Gateway PID file already exists in ‘/path/to/tmp/ig.pid’. Cannot start” error. -
End users cannot authenticate to AM (All versions) when Twilio is used for MFA
The purpose of this article is to provide assistance if users cannot authenticate to AM using multi-factor authentication (MFA) when Twilio is used to provide MFA or two-factor authentication (2FA) services. For example, Twilio sends one-time passwords (OTP) via SMS. -
AM (All versions) fails to start after Apache Tomcat upgrade or configuration changes
The purpose of this article is to provide assistance if you see “Failed to start connector” and “Protocol handler start failed” errors, which prevent the AM server from starting. You will notice this happens after upgrading or making changes to Apache Tomcat™. -
ClassNotFoundException error after installing WebLogic Java Agent 5.10.x, 2023.3 or 2023.6
The purpose of this article is to provide assistance if you encounter a "java.lang.ClassNotFoundException: org.apache.log4j.Category" error and the WebLogic console fails to load after installing the WebLogic Java Agent.
Additional Resources
Identity Gateway(IG)
Documentation
Knowledge Base
Acess Manaement (Self Managed)
Documentation
Knowledge Base
Community
Twillio