We want to rebuild our native apps (iOS and Android) to OutSystems. We think on forehand we'll come a long way. There's one thing we can't get our heads around:
We make use of an external IAM provider (Thales) https://thalesdocs.com/oip/mobile-id/index.htmlThey provide some SDK's to make use of their 'tooling'. Android, iOS, React Native JS and a Flutter plugin.
Our question is, how do we proceed from here? What are our options?We thought of some, but please assist. Maybe there are some options we didn't come up with? We don't even know if these options are valid posibillities..
1. Build a native iOS and Android app where the authentication is handled, then redirect somehow to the OutSystems app?2. Rebuild an SDK on our own and implement it in OutSystems? 3. Install both Android and iOS SDK's?
There are some reasons why we can't ask our current app developers what option we should choose, or if there are more options.
It seems that apart from authenticating users from Thales, you need some more functionalities to use in the Outsystems App. Is that correct? If so, you need to check the Thales documentation to see if they provide APIs for these functions.
Well. As usual.... It depends :-) In this case on your concrete requirements on HOW a user should authenticate.
The easiest way is to configure a new application registration in Safenet for Authorization Code flow and use the the OIDC Mobile Forge component, or you build it yourself with the InApp browser forge component. But as said, it depends on how your authentication scheme should look like.
Stefan
Integrating an external IAM provider into OutSystems mobile apps can be easily implemented. I recommend leveraging the InApp Browser Plugin to handle authentication within the OutSystems Mobile App.
To enable this, you can include a Login button within your OutSystems application. When users click the Login button, the InApp Browser plugin can be used to redirect them to Thales for entering their Thales credentials. Upon successful login, the user can be seamlessly redirected back to the home page of your OutSystems app.
By using the InApp Browser Plugin, you can simplify the authentication process for users, allowing them to securely authenticate with Thales while staying within the OutSystems mobile app environment.
Ok, thanks for the replies @Stefan Weber and @Abhishek Hayaran
But what about the build in functions Thales offers, like the way the username and password is hashed, the device registers itself in the Thales tooling our support desk uses, the fingerprint and pincode rules. We have to built al that ourselfs right?
Yes indeed, they have beside authentication way more functionality in their SDK we use now and need to use in the future. But it's clear to me. There's no way we can use those SDK's in anyway and we need to build all functionality ourselfs. That's a bit what I was afraid for. Not that we can't build it.. more that we don't want to build it and run it ourselfs (that's why we bought the service).