由于Azure的端点域:哈希与* .onmicrosoft [英] Given Azure Endpoint Domains: Hash versus *.onmicrosoft

查看:121
本文介绍了由于Azure的端点域:哈希与* .onmicrosoft的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我创建一个web应用程序与Azure的AD工作。

I'm creating a web app to work with Azure AD.

我经历使得REST请求,等的过程中,我感到有点困惑,到公元给出与那些在的帮助文档与我所给出的AD控制台联机。在一些文件页面,端点给定为 https://login.windows.net/ [某些域] .onmicrosoft / ...,其中对AD控制台,我给一个长哈希值,没有.onmicrosoft / ...present。我在使用了这两个问题(别的东西显然是错误的),但我不能进行调试的,直到我知道我应该继续,所以我知道这是不是造成问题的原因。

I'm going through the process of making the REST requests, etc., and I'm a bit confused as to the endpoint URL parameters given by AD versus those given in the help documentation versus what I'm given in the AD console online. On some of the documentation pages, the endpoints are given as "https://login.windows.net/[some domain].onmicrosoft/...", where on the AD console, I'm given a long hash, with no ".onmicrosoft/..." present. I'm having problems with both (something else is obviously wrong), but I can't proceed debugging that until I know which I should proceed with, so I know that this isn't causing the problem.

推荐答案

这确实混乱,没有很好的哈希出来的文档。

This is indeed confusing and not well hashed out in the documentation.

我已经创建了一个网络应用程序,也使用Office 365的身份验证Azure的AD,和我使用了Azure的AD控制台对我的端点的URL生成的散列,一切运作良好。无论AD控制台提供了在线是正确的,并会为您的特定的应用程序(给出的哈希值,其实是更换.onmicrosoft域,将工作做好)。

I've created a web-app that also uses Office 365 authentication with Azure AD, and I am using the hash generated by the Azure AD console for my endpoint URLs, and everything is functioning well. Whatever the AD console gives you online is correct, and will work for your particular app (the hash given is in fact replacing a .onmicrosoft domain, and will work well).

这篇关于由于Azure的端点域:哈希与* .onmicrosoft的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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