13
Views
4
Comments
Solved
Integrated Windows Authentication for Reactive Web
Application Type
Reactive

Is there any reason Integrated Windows Authentication is not supported for Reactive Web (as it has been for Traditional Web)?

Can it be expected in the nearby future?

(Unfortunately I was not aware of this constraint and now run into some project planning difficulties).

Staff
Rank: #20
Solution

Hi Ahron,

To be completely honest with you, having Windows Integrated Authentication built-in on reactive is not something in our short/mid term roadmap (although we may give ways to do it trough extensibility). 

This being said, you can still use a traditional screen that requires it in your reactive authentication flow, login there on preparation (using the username you get from the IntegratedSecurityGetDetails) and redirect back to a reactive screen. As long as you have single sign-on between app types turned on, the user should arrive to the reactive screen already authenticated.

Cheers,
Tiago Simões

Rank: #153
Rank: #24729

Thank you Agno, however using Azure AD or AD FS/SAML2 currently is no option in my project.
The question is more about the reasons why and whether anyone knows if we can expect Integrated Windows Authentication support for Reactive Web in the future.

Staff
Rank: #20
Solution

Hi Ahron,

To be completely honest with you, having Windows Integrated Authentication built-in on reactive is not something in our short/mid term roadmap (although we may give ways to do it trough extensibility). 

This being said, you can still use a traditional screen that requires it in your reactive authentication flow, login there on preparation (using the username you get from the IntegratedSecurityGetDetails) and redirect back to a reactive screen. As long as you have single sign-on between app types turned on, the user should arrive to the reactive screen already authenticated.

Cheers,
Tiago Simões

Rank: #24729

Thank you Tiago, for your sharing future prospects and your suggestion to mix a traditional log-in page with Reactive Web under single sign-on (another possible solution - in addition to Agno's suggestions using Azure AD or implementing AD FS/SAML2.0).