Issue
- While configuring Sharepoint integration following this documentation, we are facing the following HTTP 500 internal server error, and found that we have multiple versions of the connector installed.
[http-nio-8080-exec-3][code_jsp:163] {code="500", msg="", uri=/c/document_library/sharepoint/oauth2} javax.servlet.ServletException: java.lang.ClassCastException: class com.liferay.sharepoint.rest.repository.internal.document.library.repository.authorization.oauth2.SharepointRepositoryRequestState cannot be cast to class com.liferay.sharepoint.rest.repo sitory.internal.document.library.repository.authorization.oauth2.SharepointRepositoryRequestState (com.liferay.sharepoint.rest.repository.internal.document.library.repository.authorization.oauth2.SharepointRepositoryRequestState is in unnamed module of l oader org.eclipse.osgi.internal.loader.EquinoxClassLoader; com.liferay.sharepoint.rest.repository.internal.document.library.repository.authorization.oauth2.SharepointRepositoryRequestState is in unnamed module of loader org.eclipse.osgi.interna l.loader.EquinoxClassLoader)
Environment
- Liferay Quarterly releases
Resolution
- The documentation describes how to install the connector when it is not available out of the box in the used Liferay version, which is a mandatory step before starting to configure it.
- If the connector is already available in the Liferay version used, this part need to be skipped.
- To confirm the availability of the connector, you can check
liferay/osgi/marketplace
folder if it contains Liferay REST Connector for SharePoint or runlb | grep Sharepoint
in Gogo Shell.