Skip to main content

I am trying to achieve integration between Thinkwise applications and Office 365.

The problem I encounter is that the Authorization protocol OAuto 2.0 does not seem to be supported by the HTTP connector in process flows. 

The ultimate goal is to come to a solution where end users can independently set up PushNotifications in Office 365, for example if files are added in Sharepoint, incoming E-Mail messages, integration with MS Teams, etc.

I guess that once the authentication OAuto 2.0 type is available, connections with others platforms like Google and Dropbox, will be possible too.

 

 

 

Hi Harm,

Have you tried implementing the OAuth authentication flow yourself using the OAuth2 bearer token approach? This should be possible. 

https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow

 

Hello Jasper, 

This idea was mentioned before, bij Vincent Doppenberg more than a year ago. I have tried this.

Spend several days on it, also half a day with a Thinkwise senior specialist. Finally came to the conclusion that this is not possible. 

There is one step in the authentication cycle, which cannot be taken inside the GUI. 

Maybe I need more information about process flows and the HTTP connector. 

Ideally, it should be as easy as how this is done in Postman.

If you are sure, it is already possible in the SF, can you drop a step-by-step instruction in the portal? 

 

 

 

 

Hi Harm, 

We’ve added instructions on how to authenticate using Microsoft Graph Application permissions to the docs: https://docs.thinkwisesoftware.com/docs/kb/microsoft_graph.html.

Getting access on behalf of a user, using Delegated permissions, is indeed not possible yet as we need to redirect the user to the OAuth provider’s login page.

Thank you for the clear explanation in the Docs. 

The scenario's we see most added value, are with access on behalf of end users. Once this becomes available, we can start the implementation of various outstanding ideas.

 

 

 

The possibility of using OAuth 2.0 would be really appreciated by us as well. We would like to connect to the banks for retrieving account and payment information, as well as initiating payments. The API's used by the banks require OAuth 2.0. So, vote +10 :-)

Updated idea status On the backlog → Working on it!

In the 2021.2 version of the Thinkwise Platform, we've added 2 new connector process actions: OAuth login connector and OAuth refresh connector. For each process action, input and output parameters are added.

Both process actions need a OAuth server configuration to work. These servers can be configured in the new OAuth servers tabpage in the Project versions screen. It is also possible to override these settings:

  • In the SF, for development/testing purposes. This can be done in the new OAuth servers tabpage in the Runtime configuration screen.
  • In IAM, to make it application specific. This can be done in the new OAuth servers tabpage in the Applications screen.
Updated idea status Working on it! → Next release
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Updated idea status Next release → Completed

@Jeroen van den Belt Could you give a explanation on how to implement the new OAuth features?

Terms & ConditionsCookie settings