[Microsoft Login Connector] Using in reactive web apps

Forge Component
(10)
Published on 10 Feb (9 days ago) by Paul Davies
10 votes
Published on 10 Feb (9 days ago) by Paul Davies

Hi all,

We are aware that the connector doesn't have a pattern for Reactive web apps.  This is being looked into with hopefully an update soon.

 

I've had a quick look at options and it looks like the best way to proceed is to build a reactive forge component from the ground up. This will take a bit of time as you can't cut and paste between traditional web projects and reactive projects.  Explored building a wrapper to generate the logon button block, but session variables got in the way.  Will look to rebuild over the coming days and publish separately.

Thanks

Paul - Davies March 

All,

Exciting news the good folks on the MS Login team have just released a reactive version of the connector.  It can found here.

https://www.outsystems.com/forge/component-overview/6933/microsoft-login-connector-reactive

Thanks to Miguel Amado and the team for getting this out.

 

Good Job Guys!

A few questions

  1. Now that the server logic is available in a separate service application, will the original Microsoft Login Connector be refactored to use it too?

  2. In the application Microsoft Login Connector Reactive, there is still the server action SyncAzureRoles, but not used, as it is now defined and used in Microsoft Login Connector Core application. Could it we removed?

  3. Is it possible to have in both applications module the unused dependencies be removed? especially the dependency to OutSystems Charts is not required.

Regards,

Daniel

Paul Davies wrote:

All,

Exciting news the good folks on the MS Login team have just released a reactive version of the connector.  It can found here.

https://www.outsystems.com/forge/component-overview/6933/microsoft-login-connector-reactive

Thanks to Miguel Amado and the team for getting this out.

 


Thanks Paul

Does anyone know of any documentation detailing how to actually implement this component in Service Studio? The documentation on the Forge only seems to deal with the Azure side of things. I've registered the URL and have a Client ID and Client Secret, now what...

Also, the documentation on the forge seems to have just been copy & pasted from the traditional web version so I think it may contain some errors as a result. 


Should:

https://<your outSystems Server>/MicrosoftLoginConnector/Callback.aspx.

not be:

https://<your outSystems Server>/MSLoginConnectorReactive/Callback

?


Any help would be greatly appreciated

Many thanks

Richard