SAP Mobile cards: Automatically logged out/ Error message handling

[c_drancourt]

Hello everyone (and Happy new year),

I am currently investigating SAP mobiles cards and managed to create a card for purchase requisition approval with 2 actions approve and refuse. This has been done on a SCP trial with a cloud connector connected to our backend. They are working fine but I'm having some small issues to fix:

1) The app is installed on my phone (Android). I need to scan the QR code to assign my account to my phone which is fine. But if I'm checking the sap mobile card app on my phone, let's say 2 hours later, I'll need to scan the QR code again to be able to check it. Seems like I'm automatically unlogged and do the whole login again. I'm quite sure that my users won't like to be forced to scan the QR code anytime they're willing to check their cards. Is it because I'm working on the trial? Will it work fine on a productive system? Any ideas on what is happening?

2) When refusing the PR approval from the card on a PR which is blocked by a user, I receive a 400 - Bad request which leads to an generic error on the phone such as "Action can't be done" instead of "PR is blocked by another user". Is there a way to handle errors when calling actions in mobile cards?

Thanks for your help.

Christophe

[c_drancourt]

I'm bumping on this for a related question: users seems to have to login manually with their whole username + password. Is it possible to activate the digital print instead for sap mobile cards? Just as for hybrid apps.

Thanks.

[Jitendra_Kansal]

Christophe DRANCOURT

1. I doubt this could be due to refresh token lifetime set in Mobile Cards app in your CP account.

Can you look into settings -

Mobile Services Cockpit > SAP Mobile Cards > Feature > Security

you can increase Refresh Token Lifetime

(in my trial account, i have it - access token 3 days, refresh token timeline 365 days)

You can enable biometric authentication as well - go to Mobile Services Cockpit > SAP Mobile Cards > Feature > Client Policies > Enable Passcode Policy and select "Biometric authentication" .

In Mobile Cards app settings > make sure to enable "unlock app with Biometric ID" option

2. I am not sure about this, i would suggest you to raise this here https://influence.sap.com/sap/ino/#/campaign/1580

Regards

JK

[pjcools]

Hi Christophe

Probably a bit late now for HNY 🙂 but hope 2019 is going well anyway. Did not see this previously - not sure if you tagged it in the mobile services space or not but I have seen this now. You may want to add this tag to get others to view and offer their advice.

On 1) I can confirm that when on a productive account you will not be required to login again and this is the same experience whether you use the SAP Cloud Identity Authentication Service (SCIAS) or MS ADFS for your organisation. Any other iDP should be fine as well. My experience has been that when you first use the QR code you will be required to sign in but after that you will not. The only instance where you need to login again is if you reset the application entirely in the Settings of the application itself.

On your subsequent note - don't start the application directly as it will ask you to login with your SAP Cloud Platform credentials. The best way is to scan the QR code and this will then prompt you to run the SAP Mobile Cards application so follow that through and you will then be asked for the credentials as configured. In my set up we are using MS ADFS so I need to supply my credentials for ADFS once and then it is fine after that.

On 2) The mobile cards performs the action in the backend OData service so it would still provide all of the normal error handling in transactions such as /n/IWFND/ERROR_LOG and /n/IWBEP/ERROR_LOG so I would suggest you go there to double check if any errors have been recorded. Additionally, in mobile services you can set a trace for the user to get more detailed error messages. When in Mobile services, choose Analytics -> Network traces. You can then enter the username and set a limit (2KB or 1 hour) and then start recording. You can then perform the actions and then come back and view the file to see what is going on.

I've been using SAP Mobile cards for some months now and it works really well so I hope you get these issues sorted out.

Please mark this as Best Answer if this solves your issues. Thanks!

Kind Regards

Phil Cooley