简体繁体 English

仅使用Keystone进行Wirecloud身份验证？

[英]Wirecloud authentication using keystone only?

原文 2016-01-28 10:20:27 2 1 django/ fiware/ fiware-wirecloud

The instructions for providing FIWARE based authentication for Wirecloud suggest installing KeyRock (a frontend/backend combo of the Horizon/Keystone GE). 该指令为Wirecloud提供基于FIWARE认证建议安装KeyRock（地平线/梯形校正GE的前/后端组合）。 Is the frontend (Horizon) really necessary if the only application to be secured is a Wirecloud instance (and possibly some backend services). 如果唯一要保护的应用程序是Wirecloud实例（可能还有一些后端服务），那么前端（Horizon）是否真的必要？ The point is to avoid, if possible , to have to configure/style/maintain etc. a second frontend. 关键是要尽可能避免配置/样式化/维护等第二个前端。 Is it possible to authenticate directly using a Django plugin like this ? 是否有可能直接使用Django的插件，像验证这样？ Pros and cons? 利弊？

1 个解决方案

WireCloud is currently linked to the use of django.contrib.auth , any authentication plugin based on it should work. WireCloud当前已链接到django.contrib.auth的使用，基于它的任何身份验证插件都应该可以使用。 Moreover, the instructions for using KeyRock are using python-social-auth so, in fact, you can use it for authenticating using any of the backends supported by python-social-auth : GitHub, Twitter, OpenId, ... 此外，使用KeyRock的说明使用的是python-social-auth因此，实际上，您可以使用它来通过python-social-auth支持的任何后端python-social-auth ：GitHub，Twitter，OpenId等。

In that regard, I don't see any problem in the use of the plugin you are proposing (Although I have not tested it). 就这一点而言，我在使用您建议的插件时没有发现任何问题（尽管我尚未对其进行测试）。

The advantage of using the KeyRock backend provided by WireCloud is that it enables operators and widgets to propagate the credentials to third-party services using KeyRock for authentication (eg Orion Context Broker, Object Storage, ... and in general, any service behind a PEP proxy). 使用WireCloud提供的KeyRock后端的优势在于，它使操作员和小部件能够使用KeyRock进行身份验证将凭据传播到第三方服务（例如Orion Context Broker，Object Storage等），通常， PEP代理）。