Hi Kevin,

Maybe the IDP forge component

https://www.outsystems.com/forge/component-overview/7090/idpreact

Regards,

Leandro.

Hi Leonardo,

I think Kevin means integrated windows authentication.

Regards,

Daniel

Hello Kevin,

I assume you mean the fact that this is missing from React applications?

Daniël, I think your link is wrong there, it points to "https://integrated%20windows%20authentication/"

Hi Craig, i fixed the link, thanks for pointing that out.

Hi,

I mean integrated windows authentication.

And like Craig said, this is missing in react application.

Hi,

React applications are like Mobile Apps, so haven't Integrated Authentication option too on a screen properties.

I guess the authentication configuration would be the defined in the Users application, wouldn't?

Or IDP component for other authentication services.

Regards,

Leandro.

Hi, there is no these option entries in Reactive App. Please advise how to use idpReact forge

Hi Jessica,

How to use IDP(React) is described in its very extensive documentation: https://www.outsystems.com/forge/Component_Documentation.aspx?ProjectId=599&ProjectName=idp

Note that this is not something like Integrated Authentication. You will need an authentication provider that can use SAML, this is not something AD supports out-of-the-box. 

Regards,

Vincent Koning

Thank for yr response. 

However, this documentation is for implementing a traditional web app. 

May you advise how to apply it in the reactive web app (it hasn't 'NoPremission' and 'LoginInfo') ?

Hi Jessica,

I don't use this component anymore myself but the component uses the iDP itself as the configuration host. You then need to use the demo app (since no other documentation is available) to figure out the needed changes. This can be read on the forge components details. 

The last time I used this component it was very easy to use (but it didn't match my requirement so I went for something else instead). Please download the demo app, investigate it and if you have any questions then please post these.

Hi Jessica,

Some more information. If you don't have a SAML provider for you (presumable) Active Directory you need to install ADFS into your environment (Or use Azure AD for example should you have that up-and-running). You can get instruction on how to install these here: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/deploy-and-configure-ad-fs

Should you already Azure AD in place you can also use the Microsoft Login Connector component. This allows uses to login via the oAuth2 protocol (something alike SAML). For this you need to configure the following 3 forge components;

1. Microsoft Login Connector Core
2. Microsoft Login Connector Reactive
3. Microsoft Login Connector Management

There is documentation (but not complete) available including Demo documents. I will expand on the documentation soon but if you have any question I can answer those. 

Hi,

Does anyone know if there was some evolution in the OutSystems platform about native integration of Reactive Web applications with Active Directory?

In our environment, we have Active Directory configured on the Users module, to force Traditional Web Apps (a lot of legacy applications) to make users authenticate automatically with AD. But now one we are developing a Reactive Web, and it looks like it still doesn't work. Every time that I try to access any screen, I'm been redirect to the Users module (but logged-in). ps.: The debugger doesn't stop on the exception flow, which does not make me understand where this redirection comes from.

Thanks for any help!

Regards,

Breno.

Any update on this. We have the same situation as Breno Nico above. 

Hello,

Same issue here.

React app and always redirecting to the User app.

This has to do with the Users/IntegratedAuthentication page.

In the preparation it checks if session.LoginRedirectURL is empty (it will always be for a React app), and redirects to the GetOwnerURLPatch which will be the Users main page.

This should be an input parameter, so it would redirect to the original page you came from.

Hello,

I solved this "issue" in this way.

In summary, we had to add a button on the Login page, to redirect to a Traditional Web application that will do the integrated authentication automatically and then revert back to the original react application.

This is done fast, so the user wouldn't even notice it.

So, this traditional app, must receive the url to where you want to be redirected afterwards.

Also, in Lifetime you need to activate the option to share authentication between traditional and reactive apps, for this to work and you don't need to activate the integrated authentication in the User's app.

1) in the new traditional application, just one empty screen, and in the preparation :

A : If the user can't be authenticated will return to the login screen

B : If the user was successfully automatically authenticated, will redirect to the provided url 

The actual trick is in the User_IntegratedAuthenticationLogin action.

It's a clone of the same action in the Users application, except that it won't check if the Integrated Authentication is activated in the User's app:

Hope this helps and if anyone has a better option, please share.