本文介绍了Azure FHIR Postman oauth2不再有效的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

几个星期前,我注册了一个Azure AD应用程序,其redirect_url为https://www.getpostman.com/oauth2/callback,此时它可以正常运行。 

a few weeks ago, I register an Azure AD application, with the redirect_url as https://www.getpostman.com/oauth2/callback, at that time, it work. 

但现在当我使用邮差时,我遇到错误

But now when I use my postman, I encounter the error

" OAuth2WindowManager~startLoginWith - 网址与注册的callbackURL不匹配,因此跳过"

"OAuth2WindowManager~startLoginWith - URL did not match the registered callbackURL, so skipping"

任何建议?  ;

any suggestions? 

致力于APIM

推荐答案

看起来你的网址中有两次oauth2,你确定这是正确的授权端点吗?似乎oauth2 / authorize部分被附加到回调网址。 看起来你也试图按照
的响应类型遵循授权代码流。 

It looks like you have oauth2 twice in your url, are you sure that's the correct authorize endpoint? It seems like the oauth2/authorize section was appended to a callback url. It also looks like you're trying to follow the authorization code flow per the response_type. 

请查看v2.0端点的验证码流文档,并确保您正确关注流程: 

Please take a look at the auth code flow docs for the v2.0 endpoint and make sure you are following the flow correctly : 

https://docs.microsoft.com/en-us/azure/active-directory/develop / v2-oauth2-auth-code-flow





这篇关于Azure FHIR Postman oauth2不再有效的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-23 05:33