User is running SAP Mobile Platform 2.3.3 and developing Native MBO applications for iOS and Windows Mobile devices. They utilize the following EIS - MS-SQL Server database, SAP, REST Services and SOAP Services. Both the MS-SQL and SAP EIS systems trigger Data Change Notifications using the HttpAuthDCNServlet to keep the cache in sync with backend changes. The application in SAP Mobile Platform utilizes a HTTP Authentication security configuration that points to a custom HTTP service they have written that validates user credentials and returns list of roles mapped to the user.
The authentication cache on the HTTP Authentication security configuration is set to 20 minutes. The user has seen that SAP Mobile Platform caches the authentication results for device users and uses this cache to validate subsequent authentication requests until the 20 minute timeout is reached after which it makes a call again to the HTTP endpoint to re-validate the user.
This behavior makes sense but it does not work the same way for authenticating DCN requests. The user is seeing that every Data Change Notification request that is received from the backend is being re-authenticated from the HTTP endpoint instead of relying on the authentication cache. The user is passing the JSESSIONID in their Data Change Notification requests and so would have expected SAP Mobile Platform to use its authentication cache to validate subsequent Data Change Notification (DCN) requests from the same DCN user. This behavior is causing an unnecessary load on their custom service and the user would like to understand what can be done to make DCNs also leverage SAP Mobile Platform's authentication cache.
- SAP Mobile Platform 2.3.3
- Windows 2008r2
- Backend EIS MS-SQL and SAP R3
- Data Change Notification
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.