Wso2 apiman:无效请求,无效回调 [英] Wso2 apiman: INVALID REQUEST, invalid_callback

查看:27
本文介绍了Wso2 apiman:无效请求,无效回调的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想在我的 Windows 笔记本电脑中启动 apimanger,并使用自定义 URL 访问它

从日志看来,我必须替换localhost"

wso2carbon.log

TID: [-1234] [] [2020-02-29 14:06:47,948] INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - 直通 HTTP 侦听器启动0:0:0:0:0:0:0:0:8280TID: [-1234] [] [2020-02-29 14:06:47,950] 信息 {org.apache.synapse.transport.passthru.PassThroughHttpMultiSSLListener} - 正在启动直通 HTTPS 侦听器...TID:[-1234] [] [2020-02-29 14:06:47,960] INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - 直通 HTTPS 侦听器于 0:0:0 启动:0:0:0:0:0:8243TID: [-1234] [] [2020-02-29 14:06:48,516] INFO {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - 任务服务以独立模式启动...TID: [-1234] [] [2020-02-29 14:06:48,588] INFO {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent} - 成功在注册表上初始化事件TID: [-1234] [] [2020-02-29 14:06:49,021] INFO {org.wso2.carbon.core.init.JMXServerManager} - JMX 服务 URL : service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmiTID:[-1234] [] [2020-02-29 14:06:49,027] 信息 {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - 服务器:WSO2 API Manager-3.0.0TID: [-1234] [] [2020-02-29 14:06:49,029] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2 Carbon 在 216 秒内启动TID: [-1234] [] [2020-02-29 14:06:50,175] INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - 管理控制台 URL : https://<host>:9443/碳/TID: [-1234] [] [2020-02-29 14:06:50,177] 信息

需要进行哪些配置更改?

解决方案

这里有一个解决方案

转到此网址:

我可以访问/devportal

I want to start the apimanger in my windows laptop, and access it with a custom url

From logs, it looks like I have to replace "localhost"

wso2carbon.log

TID: [-1234] [] [2020-02-29 14:06:47,948]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTP Listener started on 0:0:0:0:0:0:0:0:8280
TID: [-1234] [] [2020-02-29 14:06:47,950]  INFO {org.apache.synapse.transport.passthru.PassThroughHttpMultiSSLListener} - Starting Pass-through HTTPS Listener...
TID: [-1234] [] [2020-02-29 14:06:47,960]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTPS Listener started on 0:0:0:0:0:0:0:0:8243
TID: [-1234] [] [2020-02-29 14:06:48,516]  INFO {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} - Task service starting in STANDALONE mode...
TID: [-1234] [] [2020-02-29 14:06:48,588]  INFO {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent} - Successfully Initialized Eventing on Registry
TID: [-1234] [] [2020-02-29 14:06:49,021]  INFO {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL  : service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
TID: [-1234] [] [2020-02-29 14:06:49,027]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server           :  WSO2 API Manager-3.0.0
TID: [-1234] [] [2020-02-29 14:06:49,029]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2 Carbon started in 216 sec
TID: [-1234] [] [2020-02-29 14:06:50,175]  INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL  : https://<host>:9443/carbon/
TID: [-1234] [] [2020-02-29 14:06:50,177]  INFO 

What config changes need to be made?

解决方案

Here is a workaroud

Go to this url:

https://yourhost:9443/carbon/oauth/edit.jsp?appName=admin_admin_publisher

Replace this regexp in callback uri that has localhost:

regexp=(https://localhost:9443/publisher/services/auth/callback/login|https://localhost:9443/publisher/services/auth/callback/logout)

Corrected regexp:

regexp=(https://yourhost:9443/publisher/services/auth/callback/login|https://yourhost:9443/publisher/services/auth/callback/logout)

I hope wso2 fixes this so we don't need to hack:

I'm able to get to /devportal

这篇关于Wso2 apiman:无效请求,无效回调的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆