简体   繁体   English

WSO2 API管理器和Identity Server集成

[英]WSO2 API manager and Identity Server Integration

I tried to integrate wso2IS 5.0.0 and wso2AM 1.7.0 by following documentation. 我尝试通过以下文档集成wso2IS 5.0.0和wso2AM 1.7.0。 https://docs.wso2.com/display/CLUSTER420/Configuring+the+Identity+Server+5.0.0+with+the+API+Manager+1.8.0+or+1.7.0 https://docs.wso2.com/display/CLUSTER420/Configuring+the+Identity+Server+5.0.0+with+the+API+Manager+1.8.0+或+1.7.0

But following exception caused 但是以下异常导致

[2016-11-29 15:31:02,320] ERROR - RegistryContext Couldn't find db configuration 'wso2registry'
[2016-11-29 15:31:02,422] ERROR - EmbeddedRegistryService Failed to configure the embedded registry. Invalid data access manager.
[2016-11-29 15:31:02,429] ERROR - RegistryCoreServiceComponent Failed to activate Registry Core bundle
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to configure the embedded registry. Invalid data access manager.
        at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.configure(EmbeddedRegistryService.java:167)
        at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.<init>(EmbeddedRegistryService.java:99)
        at org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.getEmbeddedRegistryService(RegistryCoreServiceComponent.java:630)
        at org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.buildRegistryService(RegistryCoreServiceComponent.java:563)
        at org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.activate(RegistryCoreServiceComponent.java:117)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
        at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
        at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
        at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
        at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
        at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
        at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
        at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
        at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
        at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:70)
        at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2016-11-29 15:31:02,463]  INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2016-11-29 15:31:11,313]  INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined

The issue is that you have removed below section from registry.xml 问题是您已从registry.xml删除了以下部分

<dbConfig name="wso2registry">
    <dataSource>jdbc/WSO2CarbonDB</dataSource>
</dbConfig>

Th doc you are referring explicitly says not to do that. 您所指的文档明确表示不要这样做。

When doing this change, do not replace the existing for "wso2registry". 进行此更改时,请勿替换现有的“ wso2registry”。 Simply add the following configuration to the existing configurations. 只需将以下配置添加到现有配置即可。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 oAuth2 - WSO2 API Manager和Identity Server集成 - oAuth2 - WSO2 API Manager and Identity Server Integration 集成 wso2 身份服务器和 api 管理器 - integrating wso2 identity server and api manager 使用 WSO2 Identity Server 和 WSO2 API Manager 保护后端 - Securing backend with WSO2 Identity Server and WSO2 API Manager 使用WSO2 API管理器替换WSO2身份服务器 - Replacing WSO2 Identity Server with WSO2 API Manager WSO2 Identity Server和WSO2 API Manager集成-java.rmi.server.ExportException:端口已在使用中:9999; - WSO2 Identity Server and WSO2 API Manager integration - java.rmi.server.ExportException: Port already in use: 9999; WSO2 Identity Server和WSO2 API Manager集成-错误:传输错误202:绑定失败:地址已在使用中 - WSO2 Identity Server and WSO2 API Manager integration - ERROR: transport error 202: bind failed: Address already in use 使用API​​ Manager将WSO2 Identity Server配置为密钥管理器 - Configuring WSO2 Identity Server as Key Manager with API Manager 适用于API管理器和身份服务器的WSO2 SAML SSO / SLO - WSO2 SAML SSO/SLO for API Manager and Identity Server 带有独立外部身份服务器的 WSO2 API 管理器 - WSO2 API Manager with separate, external Identity Server WSO2 API Manager(和Identity Server)上的令牌验证 - Token validation at WSO2 API Manager (and Identity Server)
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM