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.
Page 1 / 1
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.
What is the exact goal that you're trying to achieve? Do you want a different application to communicate directly with a Thinkwise application through the use of OpenID? Or am I interpreting it wrong?
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
Hi @tiago,
Since you’re now able to proceed with Freddy's solution, I’ve marked your response as the best answer.
However, we’d still appreciate it if you could share what the issue was and why the documentation didn’t meet your needs. Your feedback could help us make improvements.
Jeroen
Hi All, sorry for the late response. Thank you all for trying to help.
What helped me in an implementation was this site of Manage Engine:
I thought it was a very comprehensive story that doesn't presume a certain level of knowledge on the matter.
In general, where I loose a lot of time is that the documentation gives me a direction, but it still leaves a lot of room for interpretation and there are many variables that can go wrong. Basically I find myself doing trial and error on all the combinations and hope I be lucky. With the amount of variables on this subject< I was not able to get it working without freddies help.
With a basic explanation of how Oauth works, ( I believe it deserves an elaborate video with use cases) and detailed use cases to test (why not creating a test set up of two thinkwise applications where one acts as the id provider for the other?) so starters can grow faster.
In this, and other moments it would be so nice if the tool could show what is happening. I know that you're working on it, and it has improved greatly woth the live error log, and the process flow. On the other hand, sometimes you just want to see what is going on, so you debug easier.
examples today: I was trying to grab my head around why a very simople task was not working. After a lot of time I remembered that the last time I had set the user to test a role, which was implicating. If step by step this would be possible to create, to show as many variables as possible to debug, would be such a relief.
Check here how a lowcode platform Flutterflow dealt with this necessity of there community users. on the left screen you can open a debug pane showing live what the variables are:
I hope this helps to make Thinkwise every time more acessible for more junior developers and business oriented consultants to be able to play more and more with thinkwise as well.
@tiago Thanks for your reply! Input like this helps us to improve the documenation.
Hopefully, we’ll be able to assist you better with your question then.
.