无法将 Identity Server 5.0.0 配置为 API 密钥管理器

Failed to configure Identity Server 5.0.0 as API Key Manager

我按照文档将 Identity Server 5.0.0 配置为 API(1.80) 密钥管理器 - https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager,并在安装 API 密钥管理器功能后记录启动时显示的异常身份服务器。例外情况如下:

ERROR {org.wso2.carbon.registry.indexing.RegistryConfigLoader} -  org.wso2.carbon.apimgt.impl.indexing.indexer.WSDLIndexer is not found in classpath. Please check whether the class is exported in your OSGI bundle. {org.wso2.carbon.registry.indexing.RegistryConfigLoader}
java.lang.ClassNotFoundException: org.wso2.carbon.apimgt.impl.indexing.indexer.WSDLIndexer
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    at org.wso2.carbon.registry.indexing.RegistryConfigLoader.<init>(RegistryConfigLoader.java:132)
...

ERROR {org.wso2.carbon.registry.indexing.solr.SolrClient} -  Could not instantiate Solr client {org.wso2.carbon.registry.indexing.solr.SolrClient}
java.lang.RuntimeException: java.io.FileNotFoundException: D:\wso2\wso2is-5.0.0\solr\data\index\_7.fnm (The system cannot find the file specified)
    at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1068)
    at org.apache.solr.core.SolrCore.<init>(SolrCore.java:579)
    at org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:137)
    at org.wso2.carbon.registry.indexing.solr.SolrClient.<init>(SolrClient.java:90)

...

有人可以帮忙吗?我将不胜感激。

我相信我已经找到问题所在。本文安装Key Manager功能,安装Key Manager后安装WSO2 Identity Manager Service pack时,/repository/components/plugins目录下有两个文件:

org.wso2.carbon.registry.indexing_4.2.1.jar org.wso2.carbon.registry.indexing_4.2.2.jar

我通过删除 4.2.1 jar 版本并保留 4.2.2 jar 版本解决了这个问题。这样做之后,没有遇到错误。