Hi, Camil.
You should listen to Mike's advices, using `acr_values` parameter is the way to ask Gluu to use specific auth method. I just wanted to make clear my statement (it seems you get it wrong a bit):
>In our mobile application we're able to provide a much better user experience by doing "native" integration of our app with 3rd parties SDKs (that includes Google, Facebook etc... as external identity providers). Showing even a simple login screen is not an option actually.
>If I'm not mistaken, the same login screen is being used to login our IT admin (that will be managing our Gluu instances), and our app "users". Ideally we would like to have a different client profile for separation of concerns.
No problems here, you can still do all of these. First, you may create custom login pages for each script (and steps of the script). Then you may select a specific script with `acr_values` parameter as Mike suggested. Second, my point was that your native app could silently download some simplistic login page with a singe login form, put all parameters you need in the form's fields, then submit it behind the scene to your custom auth script for processing. You don't need to show this page to a user.