Skip to Content

Another excellent article by Jan Schober of the global mobility swat team this time on how to avoid repeating Credential Request for server-initiated Hybrid Apps .

I quote “The attached How to and sample describe how you can have a server-initiated Hybrid App, that uses dynamic credentials, but does not ask for these each time a notification arrives on the client. Additionally, you can then add some customization (like a jQueryMobile collapsible) UI elements in the opened screen.  This was build on SUP 2.1 ESD#3 Patch#1.” 

Jan1.png

APPROACH To overcome this unpractical entry of credentials, you are going to use the Dynamic Authentication in combination with static credentials of a technical user. The idea is to have one Master-MBO that holds the data that we want to work on and we going to add a Trigger-MBO that will take care of sending the notification to the user’s inbox without prompting for credentials using a technical user. After the notification has arrived in the user’s inbox and the user opens it and online request will be sent to the server pulling the data from the Master-MBO, using the current user’s credentials as well as the parameters provided by the Trigger-MBO.

https://cw.sdn.sap.com/cw/docs/DOC-151472

avoid repeating Credential Request for server-initiated Hybrid Apps

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply