[英]( WSO2 AM 4.1 : Token Endpoint ) Can we use the gateway as the default token Endpoint?
in new wso2 apim versions (4.0/4.1) the default token endpoint has changed.在新的 wso2 apim 版本 (4.0/4.1) 中,默认令牌端点已更改。 It used to be the Gateway: https://gw.wso2.com/oauth2/token and the the call is redirected to the key manager node.它曾经是网关: https://gw.wso2.com/oauth2/token并且调用被重定向到密钥管理器节点。 Now with the news versions, we do not need to go trough that process as we can directly call the key-manager for token operations.现在有了新闻版本,我们不需要 go 通过该过程,因为我们可以直接调用密钥管理器进行令牌操作。
is there a way to preseve the same behavior of the old versions in the new version 4.1?有没有办法在新版本 4.1 中保留旧版本的相同行为?
For now, I tried adding the TokenAPI .xml api in the synapse-configs to see if i can produce the same experience, but the api is automatically destroyed in startup.现在,我尝试在 synapse-configs 中添加TokenAPI .xml api 以查看是否可以产生相同的体验,但 api 在启动时自动销毁。
Any ideas?有任何想法吗?
Thank you in advance.先感谢您。
Best regards,最好的祝福,
Yes, the gateway removes those files.是的,网关会删除这些文件。
To keep custom runtime artifacts deployed in the Gateway, add the following configuration in the /repository/conf/deployment.toml file.要在网关中部署自定义运行时工件,请在 /repository/conf/deployment.toml 文件中添加以下配置。
[apim.sync_runtime_artifacts.gateway.skip_list]
apis = ["token_api_file_name.xml"]
Refer - https://apim.docs.wso2.com/en/latest/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup/#configure-the-gateway-nodes参考 - https://apim.docs.wso2.com/en/latest/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup/#configure-the -网关节点
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.