SMP Logout without connection

[Former Member]

Hello Everyone

I have been going through this very helpful blog on SMP onboarding using the Odata protocol - https://archive.sap.com/documents/docs/DOC-59555

I would like to know what the best way to handle the logout function is in the case where the user does not have a data connection and cannot reach the SMP server to delete his registration token.

Is there any harm to just leaving the token/registration there on the SMP server? As the user will simply get a new registration token when he logs in again.

Is there a better way to handle this scenario?

Thank you

Riaz

[Jitendra_Kansal · Accepted solution]

Hello Riaz,

Just to comment on this part:

I would like to know what the best way to handle the logout function is in the case where the user does not have a data connection and cannot reach the SMP server to delete his registration token

In my most of SMP projects,we implemented 'LogOut' functionalities only to be used when user has connectivity (calling DELETE REST API), it will delete respective SMP-AppCID

However, IMO (again), there is no harm leaving those registrations in SMP server (but yes as said by Akos its not a best way), however, you may go for 'automatic removal' option , where inactive registrations are removed automatically after a certain time.

https://help.sap.com/viewer/313e7789125149b3b5bb6f1c7e1ea322/3.0.13/en-US/cd411891b2e74310b5384426bf...

Regards,

Jitendra

[Former Member · Accepted solution]

Hi Jitendra

Thank you for pointing out that feature, I think its the best viable option for this scenario.

Regards

Riaz

[grabz]

Hello Riaz,

We don't really have a best practice for that. To leave a registration ID and always have a new one is not the best option as that can cause inconsistencies which are really hard to untie. At the comment section of the blog you are referring to there are some examples which are pretty good.

Best regards,

Ákos

[Former Member]

Hello Akos

I had a look at the comments section in more detail but I still feel like it doesn't guide me to a best practice way of handling this situation.

Do you know if its possible to call the delete registration method before the registration method and in this way first delete an old registration that was unable to be deleted before due to connectivity?

Regards

Riaz