Second time User/Server validation is not happening in SUP Odata Consumption

[raju_pvn]

Hi Experts,

We are facing a serious issue. All of a sudden our SUP OData application is not validating User or server settings while we logging in second time.

SUP Server: 2.2 Sp04

Client: IOS Native

Issue Description:

We are developing an OData based application consuming through SUP. We were able to register user and connect to sup server and fetch the data successfully from Gateway server first time. Second time if I a trying to login with invalid server settings or invalid users the SUP is not validating and bypassing to gateway and pulling data if the user is valid.

Let me know if you require more details.

Regards

Raju

[midhun_vp]

After how much time interval you are doing second login ? Are you logging out from the app for the second user login ?

[raju_pvn]

Hi Midhun,

Thanks for your quick reply.

I am logging out from the application and then trying to provide invalid settings and user, but still it is logging in without any exceptions. Yes I am logging out from the app for second user login. The logging out functionality is just screen navigation I am not doing any logic.

Regards

Raju

[former_member228049]

I'm not familiar with this part, but for diagnosis purpose , did you try to close the app ( not just logout , exit  from app ) and re-open it and then try to login with invalid user ? If that works , the authentication inform may be cached in the container ?

[raju_pvn]

Hi Yan,

We tried with killing the app from background, but still having the same issue. But when we uninstall the app and trying it is working fine for first time again. Also can you please suggest us how to clean the cache of authentication form.

Regards

Raju

[former_member228049]

Sorry, you are not using hybrid app, right ? I thought it was hybrid app. what component you used for your app, Agentry  or your own native app  ?

[raju_pvn]

Hi Yan,

We are building the Native IOS Application.

Regards

Raju

[former_member228049]

sorry, I have no knowledge of IOS native App :-(,   but just some thouhts on diagnosis,  Is there an api from sup for you do authentication ?   do you think the credential stored in the sup  sever ? if yes, try to see if there any api call to clear the cache , the last resort is to  asking technical support

[midhun_vp]

Raju,

Once you login to the mobile app your device ID and user name will be recorded in SUP server. You can see this in SCC>server>applications with a status online/offline. If you are trying to login to the app again from the same device with a different user without deleting the existing user from SCC it will not work in the desired way. In the native based on Object APIs I have used one API unregisterApplication for unregistering the user from SUP, it deleted the user existing in SUP. Once it is done different is made from same device.

But in the Odata apps I didn't find any APIs for unregistering the user while the user click on logout. So may be it will not be a possible option. Lets consider the example of released SAP standard apps. These apps are based on Odata (same as your app), here in order to login with a new user the steps were deleting the app>reinstall app from app store>delete user in SCC> login with different user from device. This means you have to do the same for a new user login. But you can search for API that is available for logout, if its there you are safe else the above mentioned steps have to be done.

- Midhun VP