I think this has to be a simple solution, but it's my first time and I can't figure out what I have to change to make this work.
I've configured the OIDC client, that works great. I can login and everyhing is working fine in my Reactive Test app. But that was not the goal, I want to make it work in a Mobile Test App.
So I set up a simple mobile app and now I want to make use of the OIDC Mobile Client. Should be easy i guess, but there's no description of how this works. So I assumed I should start the same way as for the Reactive solution.
With this configuration
I tried this plain method, but I also tried the S256 method.
With both options I get the same error. 400 bad request
So the problem is very clear, but I don't know wat to do :P
Please help.
To give an update, last week I tried to make it work with the blocks and it worked. So that's the way to use it. Don't make use of the server or client actions. Just insert the blocks on (newly created) pages.
So, I looked a bit further and I saw also the client action Get_Mobile Authorization_URL that calls the server action.
It feels this makes more sense.. But I still get the 400 error..
There are also some blocks defined in OIDCMobile.. maybe I should do something with those? This is very hard with no manual and trying. I hope someone who has made this work can help me.
Could you please assist @João Barata, as builder of this component?
Hi @CJK83 ,Apologies for not getting to this message sooner.The proper way to use the component is to use the provided web blocks on pages that are set for anonymous access.For the callback screens, you need to set an anonymous screen that needs to receive the same parameters as the corresponding callback web blocks.In any case, I've launched a new version of the OIDC mobile that has the dependencies updated to the latest version of the OIDC Client and I've also included an example application that you can use as a reference implementation