简体繁体 English

TYPO3外部认证

[英]TYPO3 external authentication

原文 2019-02-06 19:30:31 5 1 asp.net/ authentication/ typo3

We have a TYPO3 CMS to manage user base and as a portal for various user-specific information. 我们有一个TYPO3 CMS来管理用户群，并作为各种用户特定信息的门户。 We also have a separate ASP.net C# application used for charting visualization with many of the same users with a separate admin backend . 我们也有一个单独的ASP.net C＃应用程序，用于通过独立的后台管理与许多相同用户进行图表可视化。 Looking to get rid of login portion ASP.net application and use TYPO3 session authentication. 希望摆脱ASP.net应用程序的登录部分，并使用TYPO3会话身份验证。 Idea is for the user to be able to click a link within their Typo3 frontend and get directed to the ASP.net application which can then authenticate with the Typo3 session and act in accordance. 想法是让用户能够单击其Typo3前端中的链接，并定向到ASP.net应用程序，该应用程序随后可以通过Typo3会话进行身份验证并按照其操作。 Just wondering if my best bet is to write something in the ASP.net app to get the TYPO3 session cookie (is that possible?) or if I have to do something clunky like oauth2/other service 只是想知道我最好的选择是在ASP.net应用程序中写一些东西以获得TYPO3会话cookie（可能吗？），或者我是否必须做一些笨拙的操作，例如oauth2 /其他服务

1 个解决方案

I would write a TYPO3 authentication service that contacts your ASP.NET app via one of known protocols (REST?) or even custom protocol and checks authentication. 我将编写一个TYPO3身份验证服务，该服务通过已知协议（REST？）甚至自定义协议之一与您的ASP.NET应用程序联系，并检查身份验证。 If it is successful, the normal TYPO3 authentication process goes on. 如果成功，则正常的TYPO3身份验证过程将继续。

It is not enough to simply set a cookie during the authentication. 仅在身份验证期间设置cookie是不够的。 There are other things that has to be done for the user to be "set up" as logged in. 要在登录时“设置”用户，还需要完成其他事情。