跨多个域、服务总线和应用程序的 Spring Security 3.1 实现
我正在尝试找到一种在我的所有应用程序和服务总线上实现 Spring Security 3.1 的好方法。
服务巴士： REST-服务与数据库对话。这也是所有用户信息的来源。
其他应用（战争）： 我希望能够让多个应用程序驻留在不同的服务器上，所有应用程序都对用户进行身份验证并通过 Spring 的 RestTemplate 与服务总线进行通信。
问题是，当从另一个域通过 RestTemplate 进行登录调用时，Spring Security 在服务总线上创建的用户 SessionContext 是无用的。 另外，我不想为每次对服务总线的调用发送用户名和密码，然后每次都在数据库中查找。 每节课一次就足够了。
我很想听听您对我如何实施这一建议的建议。 他们在企业界如何做到这一点？ 我一直在考虑 CAS、LDAP，甚至使用 Atlassian Crowd 来实现它，但这似乎是不必要的努力。
I am trying to find a good way to implement Spring Security 3.1 across all my applications and my service bus.
Service Bus:
REST-services talking with the DB. This is also where all the user information is coming from.
Other applications (war's):
I want to be able to have multiple application stationed at different servers, all authenticating users and talking with the Service Bus through Spring's RestTemplate.
The problem is that the user SessionContext created by Spring Security on the Service Bus is useless when the login call is made via RestTemplate from another domain.
Also I dont want to keep sending the username and password for every call that I'm making to service bus, and then have that look it up in the DB every time.
One time per session should be enough.
I would love to hear your suggestions on how I could go about to implement this.
How do they do it in the Enterprice world?
I've been thinking about CAS, LDAP and even implementing it with Atlassian Crowd, but it seems like such an unnecessary effort.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论