SAP Builders Blog Posts
Learn from peers about their low-code journey and write your own blog posts to share your thoughts and experiences as you become an SAP Builder.
cancel
Showing results for 
Search instead for 
Did you mean: 
EsmeeX
Product and Topic Expert
Product and Topic Expert

mobile auth - hero image.png

Greetings Builders! This week we have released a significant feature for our customers: mobile authentication.

We have now enabled SAP Mobile Services, which authenticates end users in your native mobile applications and provides access to integrations and services from SAP Business Technology Platform. 

SAP Build Apps uses SAP Cloud Identity Services – Identity Authentication (IAS) for user authentication in the cloud. For more information on this topic, see the article: What is Identity Authentication?

Now with the ability to harness the power of Identity Authentication, you can increase the enterprise readiness of your company’s mobile apps by ensuring seamless integration with SAP Business Technology Platform. This feature allows you to reuse destinations of backend systems, which are also used for web applications and many other BTP services.

To get started with taking advantage of this feature, verify that you have Subaccount entitlements of at least 1 unit for Mobile Services (standard plan) as a prerequisite. 

auth.png

After configuring mobile authentication in your BTP Cockpit and your build settings, you can build your first mobile app with authentication services enabled. Your users will be prompted to sign in with your Identity Provider (IdP) the first time they open your app. The session will remain active until the app’s cache is cleared or the session is revoked manually.

Untitled design (10).png

👉For instructions on getting started with mobile authentication, see the documentation: SAP Build Apps – SAP Mobile Services.

We look forward to seeing our customers unlock more possibilities by enabling mobile authentication in their apps! Feel free to share any feedback or questions about this release in the comments.

Check out what else is on the horizon for SAP Build Apps this year in the Roadmap Explorer.

To see all recent SAP Build Apps releases, visit the What’s New Documentation.

7 Comments
js2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Is the passcode mandatory? Users have already gained access to the device via PIN codes or biometrics?

EsmeeX
Product and Topic Expert
Product and Topic Expert
0 Kudos

@js2 Thanks for the question - no, the passcode isn't mandatory. I've just updated the blog to reflect the updated info:

Your users will be prompted to sign in with your Identity Provider (IdP) the first time they open your app. The session will remain active until the app’s cache is cleared or the session is revoked manually.
AmgadAlamin
Discoverer

Getting the following error when trying to config Mobile Authentication. Why looking for the Standard plan when it's not a plan option now?  Available options are Resources and Free, mine is Resources.

AmgadAlamin_0-1710526580553.png

 

erickgomez-tech
Participant
0 Kudos

Hi @AmgadAlamin 

I am using the Free Service Plan, for testing, and everything went perfectly.

Mobile_authentication.JPG

Kind regards,

Erick Gómez

erickgomez-tech
Participant
0 Kudos

Hi @EsmeeX,

I made an App, and compiled it for Android and it worked perfectly.
I have BTP Authentication enabled and I am using Destination.

This is great, thank you very much for the functionality to the entire SAP Build team, and thank you very much for the announcement.

Kind regards,

Erick Gomez

SAP Business One SAP Business One Extensibility SAP Business One Cloud SAP Business One, version for SAP HANA SAP Build Apps 

maharana
Participant
0 Kudos

I have already created an app with btp authentication enabled and then i configure and build for android and everything works fine. but i am not getting the user agreement page or sign in page when i am opening my app in sap build apps preview app.

AmgadAlamin
Discoverer
0 Kudos

@erickgomez-tech ,

There was a bug with Resources plan but the team got it fixed. It works now. 

You mentioned that you consumed destinations successfully after deploying. What is your source if you don't mind? I'm using s/4hana on-premises, but I'm unable to consume my destinations.