redirect_uri阻止使基于Intranet的应用程序的能力(redirect_uri blocking ability to make intranet-based application)

 我正在开发一个基于Intranet的应用程序，我所工作的公司将会出售这些应用程序，它可以作为后台进程的一部分发布到Facebook墙上。 
 
 要授权，我需要通过流程（即https://graph.facebook.com/oauth/authorize ，参数client_id=1234567890和redirect_uri=http://customer-intranet.example.com ） - 这是第二个一个阻碍我的，因为我无法预测redirect_uri ，而且Facebook似乎对应用程序中预先指定的整个事情都很严格。 
 
 我想我需要建立一个托管网站，从Facebook接收访问令牌，然后以某种方式将该令牌重定向回客户的内部网站，在那里可以使用它。 （然后是整个离线访问令牌弃用的事情......） 
 
 我为自己做的事情太难了吗？ 有一个更好的方法吗？ 我查看了其他身份验证流程，其中，设备可能有效，但它显然处于封闭测试阶段。 

I'm working on a intranet-based application that the company I work for will sell that will have the ability to post to Facebook walls as part of a background process.
 
To authorize, I need to go through the flow (i.e. https://graph.facebook.com/oauth/authorize with parameters client_id=1234567890 and redirect_uri=http://customer-intranet.example.com)—and it's the second one that's stymieing me, because I can't predict redirect_uri, and Facebook seems to be strict about the whole thing being pre-specified in the app.
 
I'm thinking I need to set up a hosted site that receives the access token from Facebook and then somehow redirects that token back to the customer's intranet site where it can be used. (And then there's the whole offline access token deprecation thing...)
 
Am I making things too hard for myself? Is there a better way to do this? I've looked over the other authentication flows, and of them, device might work, but it's apparently in closed beta.

原文：https://stackoverflow.com/questions/9842031