Khalid,
I think Fabian's suggestion is a good one. Contrary to your comment, with Deeplink you can link to a form or a microflow. The microflow option would enable you to branch and send the user to different pages. In addition, you can configure Deep Link so that any parameters included in the URL are available inside the called microflow. I've included some information about this from the Deep Link documentation below:
Have you tried Deep Link and found that it doesn't meet your requirements? If so, perhaps you could share some information about why it didn't work for you so that the forum community can understand better what you need to accomplish.
Hope that helps,
Mike
I think this blog is a good start on how to do the automatic login: https://www.mattkdaniels.com/blogs/walkthrough-enabling-autologin-functionality-within-your-mendix-app
And you still need the deeplink module. I would extend the functionality in the link so that you not only pass a token but also some other data so you can use that redirect the user after the login to the correct page.
Regards,
Ronald
thanks for all your help so far,
So this is the scenario
Front end drupal site with links:
I click onto service B, and it redirects me into My account as this is the authentication and remembers i requested service B (this is easily done via deeplink), after clicking the login I want to then open up the B part of the application.
I tried to do this by associating the anom session with a separate entity called 'Type of service', but when you log in Mendix creates a new session and thus there is nothing to connect the original session or drupal session to the new logged in session. If you guys think i can extend the use of deep link to help me achieve the last bit that would be great, thanks.
Thanks again all for helping, it looks like the sign in microflow has solved the problem of bridging the gap between a anonymous session and a named session, thanks for all your help.
On another note, has anyone has problem with this module and Saml?