Skip to main content

Hi all. 

We have become quite experienced with the use of Thinkwise and a lowcode tool for native applications, and I'd love to combine the power of the two making Thinkwise the leading application where flutterflow connects using the openid for authentication.  

Problem is, after hours of youtube videos and documentations, I still don't feel I grasp the logic enough to turn that into an implementation. I hope someone here is able to give a light:

Example of one of the things I'd like to do: 

We created a solution where one of the functionalities is the hour registration on projects. This is done in Thinkwise, and we configured the SSO using openid connected to microsoft ENTRA. This works really well. 

I'd like to create a webapp with flutterflow where can simplify the registration of the activities via mobile phone. 

we have configured thinkwise to a point we have the openid-config (attached) 

From this point I have quite an open question: Now what? 
I'd love to have a help to get it going in insomnia to get a first understanding of how this algebra works. 

Hello tiago,

We have looked at your topic with quite a few people from our team. Unfortunately we are experiencing some difficulty while trying to get to the core of your question. So instead of an answer, I will begin by asking a couple of counter-questions to provide us with some additional insights which will hopefully help us with providing a proper answer.

The list of supported scopes and claims you provided seem fine to me, but it's hard to tell whether everything has been set up correctly without seeing IAM itself.

Hope we can get some more clarity in this topic 😅

Kind regards,

Renée


Hi @tiago,

Can you please answer the questions Renée asked? 😀 Hopefully, we’ll be able to assist you better with your question then.


@Renée Evertzen thanks for your reply. 

I've read the documentation, but I feel you must be a pro on this subject to understand it. If it works it works, otherwise its really hard to know which of the many things could have a very little thing wrong. 

Thankfully, @Freddy has been able to get it working, so I'll be copying his work for now, and hope somewhere in the middle the coin of what I'm doing drops 😂


Not the perfect solution but good to hear that you aren't stuck anymore and can continue onwards 🙂.


Hi ​@tiago, could you elaborate a bit more on what was hard to understand in the documentation or which information you were missing? That could help us to improve it


Reply