Skip to Content

As very well described by Dan van Leeuwen at Getting Started with Kapsel – Part 4 — Push, “push messages provide a way to inform or remind a user that an action should be taken by delivering a short message that appears as a notification on the device.  When clicked on, the app that is associated with the message is opened.  The Kapsel push plugin provides an abstraction layer over the Google Cloud Messaging for Android (GCM), Windows Push Notification Services (WNS) and Apple Push Notification Service (APNS).  A notification can be sent to a device registered with an application via a REST call to http://SMP_3.0_SERVER:8080/Notifications/application_registration_id. The REST call should either contain a header named X-SMP-DATA or X-SMP-GCM-DATA which includes values for the title and message content to be displayed or the values can be included in the URL.

There are three agents working on the push notification feature:

  1. The SAP Mobile Platform Server. It is responsible for gathering push notifications and device IDs from the client using the notification service provider.
  2. The Kapsel app running on the device, which is responsible for receiving the notifications.
  3. The notification service provider (APNS, GCM or WNS).

This plugin allows users or developers to register the developed app for receiving push notifications. It is also possible to process notification in the background.

The Push API offers tasks to:

  • Register or unregister for push notifications.
  • Handle push notifications.
  • Configure push notifications.
  • Handle error messages.

Proxy settings should be set in the Administration and Monitoring tool, under Settings > System > HTTP Proxy Settings in case you are using an SMP Server in a network that uses a proxy in order to have your SMP Server accessing GCM, WNS and APNS servers. Do not forget to remove these settings if the network, where your SMP Server is, is not using a proxy.

Also, do not forget to open the right ports if you are using an SMP Server in a corporate network to have push notifications working. For GCM, the 5228 and 5230 ports should be open. Check here what ports should be open for APNS.

As recommended by Dan, “for additional details see the JavaScript file in a project that includes this plugin at project_name\www\plugins\com.sap.mp.cordova.plugins.push\www\push.js or the JS Documentation at Kapsel Push API Reference.

This document is focused on Kapsel push plugin used on iOS (APNS). So, if you wish to have an example and a good document about how to use the Kapsel push plugin on Android (GCM), I strongly recommend Dan’s document: Getting Started with Kapsel – Part 4 — Push. For Windows Push Notification Services (WNS), I recommend my SCN document: [Kapsel] How to use the Push plugin on Windows.

Also note that iPhone or iPad simulators do not support push notifications, so you will need a real iOS device.

Let’s go through the steps to get it working:

  • First of all, we need to go to the Apple Developer Member Center accessing the following URL: Member Center – Apple Developer
    • To do the following steps you will need to belong to a Development Team in the Apple Developer Member Center and to be an Admin of this team.
    • Use Safari for that, because there are problems using Chrome or Firefox.
    • For more info, check Development Team.
    • Under Developer Program Resources, clickon the Certificate image.
    • Then click on Devices.
  • You will need to register your device.
    • Connect your iOS device to you Mac to check its UDID.
    • If it is not open automatically, open iTunes.
    • Click on the device icon on the top of iTunes screen. In my case, iPad icon.

Screen Shot 2015-04-28 at 5.04.00 PM.png

    • On the right side of your screen, click on Serial Number to see the UDID of your device.
    • Right-click this number and copy it.
  • Back to Apple Developer Member Center, add your device.
    • Click on the Plus button at the top of screen, close to the Add iOS Devices title.
    • Fill in a name for your device.
    • Paste your device’s UDID to the UDID field.

Screen Shot 2015-04-28 at 5.14.53 PM.png

    • Click on Continue > Register > Done.
  • On Apple Developer Member Center, add a new App ID.
    • Click on the Plus button at the top of screen, close to the iOS App IDs title.
    • Give a name to your App ID.
    • Under App ID Suffix, set the Bundle ID with the Explicit App ID option selected. This Bundle ID needs to be unique, so choose one.

Screen Shot 2015-04-28 at 6.00.22 PM.png

    • Under App Services, select the Push Notifications option.
    • Click on Continue > Submit > Done.
  • Before creating an iOS certificate, you will need to create a Certificate Signing Request (CSR) file.
    • In the Applications folder of your Mac, open the Utilities folder and launch Keychain Access.
    • Within the Keychain Access drop down menu, select Keychain Access > Certificate Assistant > Request a Certificate from a Certificate Authority.
    • In the Certificate Information window, enter the following information:
      • In the User Email Address field, enter your email address.
      • In the Common Name field, create a name for your private key (e.g., John Doe Dev Key).
      • The CA Email Address field should be left empty.
      • In the Request is group, select the Saved to disk option.
    • Click Continue within Keychain Access to complete the CSR generating process.

Screen Shot 2015-04-29 at 3.54.19 PM.png

  • Now you need to create an iOS certificate.
    • On Apple Developer Member Center, click on Certificates > Development.
    • Click on the Plus button at the top of screen, close to the iOS Certificates (Development) title.
    • Because we are not creating this sample for production, under Development, select Apple Push Notification service SSL (Sandbox).
    • Click on Continue.

Screen Shot 2015-04-29 at 3.42.45 PM.png

    • From the list, select the App ID you have created.
    • Click on Continue > Continue.
    • Click on Browse File… and select the CSR file you have generated.
    • Click on Generate.
    • Click on Download to save you iOS certificate locally.
    • Press Done.
  • The next step is to add an iOS Provisioning Profile.
    • On Apple Developer Member Center, click on Provisioning Profiles > Development.
    • Click on the Plus button at the top of screen, close to the iOS Provisioning Profiles (Development) title.
    • Select iOS App Development under Development.
    • Select the App ID you have created.
    • Click on Continue.
    • Select the certificate you have created.
    • Click on Continue.
    • Select the device(s) you have added.
    • Click on Continue.
    • Give a name to your iOS Provisioning Profile.

Screen Shot 2015-05-05 at 9.48.24 AM.png

    • Click on Generate.
    • Download you provisioning profile.
    • Finally click on Done.
    • Add the provisioning profile to Xcode by double-clicking it or dragging it onto the Xcode icon.
  • Now you need to convert you iOS certificate file to P12 format in order to use it with SMP.
    • In the Applications folder on your Mac, open the Utilities folder and launch Keychain Access.
    • Select File > Import Items… .
    • Navigate to the iOS certificate file (the .cer file) you have downloaded.
    • Select the Keys category in Keychain Access.
    • Select the private key associated with your iPhone Development Certificate (you gave a name to it 3 steps before).

Screen Shot 2015-05-05 at 11.34.05 AM.png

    • Select File > Export Items… .
    • Save your key in the Personal Information Exchange (.p12) file format.
    • You will be prompted to create a password that is used when you attempt to import this key to SMP.
  • Go through Dan’s instructions at Configuring a Kapsel App in the Management Cockpit to create an app in the Administration and Monitoring tool using the app ID name you have chosen before.
    • Do not forget that this should be also your app ID when you are creating it in the Apple website.
    • Set any URL as your OData endpoint, since we are not going to consume data at this sample app.
    • Use Basic SSO mechanism and the Default security provider.
  • Go to the Push tab. Under Apple, select Sandbox if you are testing or developing an app. Select Production if you are in a production environment.
    • For your sample app, select Sandbox.
    • Press the Browse button.
    • Select the certificate generated two steps before.
    • Press the Open button.
    • Enter the password you set for your certificate.
    • Save the configuration.

/wp-content/uploads/2015/04/push_config_694384.jpg

 

  • Now you need to add a System Login (Admin Only) authentication provider to the Notification security provider.
    • Go to Settings > Security Profiles.
    • Click on Notification.
    • Click on the Add button.
    • Set Authentication Provider as System Login (Admin Only).
    • Set the Username field as smpPushUser, the Password field as smpPushPwd and the Roles field as Notification User.
    • Click on Save > Save.
    • Restart your SMP Server.
    • This user and password will be used later to send a push notification to your device.

/wp-content/uploads/2015/04/add_auth_provider_694412.jpg

  • Create your Cordova project and add the iOS platform to it.
    • Open a Terminal.
    • If you do not have one, create a Kapsel_projects folder inside your Development folder.
    • Run the following commands in yout terminal shell, remembering to use as <APP_ID> the unique Bundle ID you registered in the Apple Developer Member Center:
      • cordova -d create <DEVELOPMENT_PATH>/Kapsel_Projects/PushDemo <APP_ID> PushDemo
      • cd <DEVELOPMENT_PATH>/Kapsel_Projects/PushDemo
      • cordova -d platform add ios
  • Add the push plugin to your Cordova project, running the following command in your terminal shell:
    • cordova -d plugin add com.sap.mp.cordova.plugins.push –searchpath <SMP_SDK_PATH>/KapselSDK/plugins/
  • In your Cordova project, replace the www/index.html by the following:
<html>
    <head>
        <script src="cordova.js"></script>
        <script>
            applicationContext = null;
            appId = "com.mycompany.push";  // Change this to app id on server

            // Optional initial connection context
            var context = {
                "serverHost": "172.25.82.195", //Place your SMP 3.0 server name here
                "https": "false",
                "serverPort": "8080",
                "user": "i828888", //Place your user name for the OData Endpoint here
                "password": "xxxxxxx",  //Place your password for the OData Endpoint here
                "communicatorId": "REST",
                "passcode": "password",  //note hardcoding passwords and unlock passcodes are strictly for ease of use during development
                "unlockPasscode": "password",
                "passcode_CONFIRM":"password"
            };

            window.onerror = onError; 

            function onError(msg, url, line) {
                var idx = url.lastIndexOf("/");
                var file = "unknown";
                if (idx > -1) {
                    file = url.substring(idx + 1);
                }
                alert("An error occurred in " + file + " (at line # " + line + "): " + msg);
                return false; //suppressErrorAlert;
            }
            
            function init() {
                if (sap.Logger) {
                    sap.Logger.setLogLevel(sap.Logger.DEBUG);  //enables the display of debug log messages from the Kapsel plugins.
                    sap.Logger.debug("Log level set to DEBUG");
                }
                sap.Logon.init(logonSuccessCallback, logonErrorCallback, appId, context);
            }
            
            function register() {
               sap.Logon.init(logonSuccessCallback, logonErrorCallback, appId, context);
            }

            function logonErrorCallback(error) {
                console.log("An error occurred:  " + JSON.stringify(error));
                if (device.platform == "Android") {  //Not supported on iOS
                    navigator.app.exitApp();
                }
            }
            
            function unRegister() {
                try {
                    sap.Logon.core.deleteRegistration(logonUnregisterSuccessCallback, errorCallback);
                }
                catch (e) {
                    alert("problem with unregister");
                }
            }
            
            function logonSuccessCallback(result) {
                console.log("logonSuccessCallback " + JSON.stringify(result));
                applicationContext = result;
            }
            
            function logonUnregisterSuccessCallback(result) {
                alert("Logon Unregistration success");
                applicationContext = null;
            }
            
            function errorCallback(e) {
                alert("An error occurred " + JSON.stringify(e));
            }

            function registerForPush() {
                var nTypes = sap.Push.notificationType.SOUNDS | sap.Push.notificationType.ALERT;
                sap.Push.registerForNotificationTypes(nTypes, regSuccess, regFailure, processNotification, "");  //GCM Sender ID, null for APNS
            }

            function unregisterForPush() {
                var nTypes = sap.Push.notificationType.SOUNDS | sap.Push.notificationType.ALERT;
                sap.Push.unregisterForNotificationTypes(unregCallback);
            }

            function regSuccess(result) {
                alert("Successfully registered: " + JSON.stringify(result));
            }
            
            function regFailure(errorInfo) {
                alert("Error while registering.  " + JSON.stringify(errorInfo));
                console.log("Error while registering.  " + JSON.stringify(errorInfo));
            }

            function unregCallback(result) {
                alert("Successfully unregistered: " + JSON.stringify(result));
            }

            function processNotification(notification) {
                alert("in processNotification: " + JSON.stringify(notification));
                console.log("Received a notifcation: " + JSON.stringify(notification));
            }
            
            function processMissedNotification(notification) {
                alert("In processMissedNotification " + JSON.stringify(notification));
                console.log("In processMissedNotification");
                console.log("Received a missed notification: " + JSON.stringify(notification));
            }

            function checkForNotification() {
                sap.Push.checkForNotification(processMissedNotification);
            }
            
           /*function showRegistrationInfo() {
                xmlhttp = new XMLHttpRequest();
                var url = applicationContext.applicationEndpointURL + "/odata/applications/latest/" + appId + "/Connections('" + applicationContext.applicationConnectionId + "')";
                alert(url);
                xmlhttp.open("GET", url, false);
                xmlhttp.setRequestHeader("X-SMP-APPCID", applicationContext.applicationConnectionId);
                //xmlhttp.setRequestHeader("Authorization", "Basic " + btoa(applicationContext.registrationContext.user + ":" + applicationContext.registrationContext.password));
                xmlhttp.send();
                var responseText = xmlhttp.responseText;
                alert(responseText);
                console.log(responseText);
            } */   
            
            document.addEventListener("deviceready", init, false);
        </script>
    </head>
    <body>
        <h1>Push Sample</h1>
        <button id="register" onclick="register()">Register</button>
        <button id="unregister" onclick="unRegister()">Unregister</button>
        <button onclick="registerForPush()">Register For Push</button><br>
        <button onclick="unregisterForPush()">Unregister For Push</button><br>
        <button onclick="checkForNotification()">Check for Notification</button><br>
        <!--<button onclick="showRegistrationInfo()">Registration Info</button><br>-->
    </body>
</html>
  • In line 10 of the copied index.html file, set serverHost as your SMP Server’s hostname or IP address.
  • Copy your www files to the iOS platform folder, running the following command in your terminal shell:
    • cordova -d prepare ios
  • Go to the <DEVELOPMENT_PATH>/Kapsel_Projects/PushDemo/platforms/ios, and open the PushDemo.xcodeproj with Xcode.
  • Use Ccode to deploy and run the project. This is how this app looks like:

IMG_0488.png

  • Click on Register for Push.

IMG_0486.png

  • Dan warns us that “when reopening the app, the Register For Push button must be pressed again or in a non-sample app, it should be called in the logonSuccessCallback method which would be called each time the application starts”.
  • The next step is to test your app. For this, you will need to send a REST request to your Kapsel app via SMP Server. So, open SMP cockpit and go to Applications > Registrations. In the Registrations table, you will find the Registration ID of your app. Take note of that ID.

/wp-content/uploads/2015/04/registration_id_715233.jpg

  • The URL you should use to send the REST request is: http://<SMP_SERVER>:8080/restnotification/registration/<REGISTRATION_ID>. The following payload: {“alert”:”<ALERT_TITLe>”, “data”:”<ALERT_DATA>” }. Set also the Content-Type as application/json.
  • When prompted for a User Name and Password enter smpPushUser and smpPushPwd.
  • Using the Advanced Rest Client chrome app, this is the result you should have:

Screen Shot 2015-06-01 at 9.56.41 AM.png

  • Note, this example may not work if the forward slash is missing from the end of the URL.
  • This is the result at you Kapsel app when it is in the foreground:

IMG_0487.png

  • When your app is in background, this is how the push notification will be shown:

IMG_0489.png

  • You can also send push notification to all devices registered for a specific app or to all the devices of a specific user. Please find more details here Notification Data Sent Using Push API.
  • Dan van Leeuwen also talks about some error codes you may have when you are sending a REST request to your app:

If the status is 403, this indicates a permission problem.  Double check that that the correct user id and password for the Notification security profile were correctly entered.  Also double check that the correct role name of Notification User was assigned to the Roles of the authentication provider for the Notification security profile.

If the status is 404, this may indicate that the app did not successfully register for notifications.  Try pressing the Register for Push button again and verify that the Successfully registered alert displays.

To report this post you need to login first.

29 Comments

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

  1. billy shen

    Hi Daniel Silva,

       very nice article, i can get the notification successfully. but the my iphone didn’t have a sound when the notification come. i have tried the payload like {“alert”:”billy test”, “data”:”hello”,”sound”: “chime.aiff” } and {“alert”:”billy test”, “data”:”hello”,”sound”: “default” } and {“alert”:”billy test”, “data”:”hello”,”sound”: “” } , all failed.

        this is the registerForPush function:

                function registerForPush() {

                    var nTypes = sap.Push.notificationType.SOUNDS | sap.Push.notificationType.ALERT;

                    sap.Push.registerForNotificationTypes(nTypes, regSuccess, regFailure, processNotification, “”);  //GCM Sender ID, null for APNS

                }


      and i am sure my iphone’s sound is open.any advice will be helpful.


    thanks,

    Billy

    (0) 
    1. Daniel Silva Post author

      Hi, Billy.

      Sorry for a late answer, but I struggled to find the reason I was having the same problem you have.

      The problem is the new API (http://<SMP_SERVER>:8080/restnotification/registration/<REGISTRATION_ID>). It has a bug that I’m opening for engineering team.

      So, try to send the push notification for the old URL: http://<SMP_SERVER>:<PORT>/Notification/<REGISTRATION_ID>. It will work.

      I hope it helps you.

      Regards,

      Daniel Silva

      (0) 
      1. billy shen

        Hi Daniel,

          thanks for your help. Very appreciate it.

          i have tried the old url, didn’t work for me. even no message came out.

          the new url :http://WIN-DTMKQF3J4UK:8080/restnotification/registration/74a79b01-a805-4190-8dc7-1288fcfae3ec.  i got message ,but no sound. the response body i got in RESTClint is <?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?><ns2:PushToRegistrationResponse xmlns:ns2=”http://mobile.sap.com/platform/server/notifications/http/dto“><status code=”0”>OK</status></ns2:PushToRegistrationResponse>

        the old url:http://WIN-DTMKQF3J4UK:8080/Notification/74a79b01-a805-4190-8dc7-1288fcfae3ec. i can’t get any message. the response body i got in RESTClint is Notification Submitted for Processing.

        both Response Header are 201.

        and the Push Url show on my SMP server is http://WIN-DTMKQF3J4UK:8080/Notification

        seems the old url didn’t work now. my smp server is SMP 3.0 SP7. any advice?

        thanks,

        Billy

        (0) 
        1. Daniel Silva Post author

          Hi, Billy.

          I’m sorry. I forgot to give you other details. Using the old API, you don’t need a payload anymore (message body). Instead of that, use the following headers: X-SMP-APNS-ALERT, X-SMP-APNS-BADGE, X-SMP-APNS-SOUND, X-SMP-APNS-DATA. I defined the value of X-SMP-APNS-SOUND as “default” and it worked for me.

          Please, try again and let me know.

          Regards,

          Daniel

          (0) 
          1. billy shen

            Hi Daniel,

               the old url works now, thanks. and how is the new api going, any progress? i do some reading on this help Notification Data Sent Through HTTP Headers – REST API Application Development (On-premise and Cloud) – SAP Library ,i didn’t find the way to send the notification to a specific user using the old api.

              you know the notification should be triggered by ABAP side, i tried find some guide, here is what i got Android Push Notification using SMP 3.0.3 and Relay Server in Kepsel Method, on this article, it says

            * set request uri (/<path>[?<querystring>])

               concatenate ‘/Notification/’ connid into l_url.  // in connid give the registration id, which got registered in SMP

            but i can’t figure out how to get the connid for each user by coding.

            if using the new api, i may put the user name to url, e.g.http://server:8080/restnotification/application/myapplicationid/user/username.

            any more guide on the backend ABAP side to call the push service?

            Best Reguard,

            Billy

            (0) 
            1. Daniel Silva Post author

              Hi, Billy.

              I’ve just informed that the issue is corrected. However, I don’t know when the new SMP Server version with this bug fix will be available. I hope soon.

              Unfortunately, today SMP doesn’t have an API to get all the registration ids of a specific app. So you will need to wait until the bug fix is available or live with push notifications without sound on iOS for a while.

              Regards,

              Daniel

              (0) 
  2. Frankie Fan

    Hi Daniel,

    I using HCPms as the notification provider, but after I click register for push. I only got the console log”PushDemo[1110:84904] DE:Registration request send  Succesfully“. I didn’t get the any response after click “register for push” button. Do you have any advice?

    (0) 
    1. Daniel Silva Post author

      Hey, Frankie.

      I’d need more info. Could you send me the server logs? Also, please check your SDK version. I’d recommend to use the last one, SP09.

      Regards,

      Daniel

      (0) 
      1. Frankie Fan

        Hello Deniel,

        Thanks for your reply . The error is because of the sdk version. Now I have using SP09PL1 and I have received the notification successfully.

        But I have another question, if I don’t use logon plugin to register to hcpms(using REST API). I cannot receive message successfully by using push plugin.

        Is that mean if we want to use push plugin, we must use logon plugin to register to hcpms?

        (0) 
  3. Frankie Fan

    Hi Daniel,

    I have encountered another problem.

    When the kapsel app is in foreground, it cannot alert the notification. But the console print the notification.

    (0) 
    1. Daniel Silva Post author

      Hi, Frankie.

      As said by Mike, please open a Discussion for your question with more details. Then paste here the link to it and I’ll be glad to try to help you.

      Regards,

      Daniel

      (0) 
  4. Andy Gonzalez

    Hi Daniel,

    Great instructions! I am able to do the register/Logon successfully, but when I do the register for push: no callback is getting called (neither success, nor failure).

    My iPad is in the VPN as I am working from home while I am trying to test this.

    Is there some settings I have to enable somewhere to allow this to happen? Or will Push just not work in the VPN?

    I have SMP 3 SP 10 for both server and sdk.

    Thanks,

    Andy.

    (0) 
    1. Daniel Silva Post author

      Hi, Andy.

      I have the same problem to test on SAP’s network. Maybe it’s because some needed port is closed.

      Have you tried to install SMP Server in your laptop? I generally do that to test it.

      Regards,

      Daniel

      (0) 
      1. Andy Gonzalez

        Thank you Daniel. That’s what I did 😉 (and so far, working great). Just wanted to see if there was some other workaround I didn’t know about.

        Thanks again,

        Andy.

        (0) 
  5. choong chan hol

    Hi Dannie,

    I’m able to send notification yesterday but failed today. Notice that Google Chrome Rest Client has updated and not able to choose the application/json.

    I try to add on the header but failed. Please help.

    new client.JPG

    Regards,

    Choong

    (0) 
  6. Óscar Yuste Romero

    I am thinking to implement Push notifications to try avoid errors in a offline application, checking changes in Backend when the user have internet connection avoiding synchronize obsolete data, do you think is a good idea?

    Thank you in advance.

    (0) 
    1. Michael Appleby

      Unless you are asking for clarification/correction of some part of the Document, please create a new Discussion marked as a Question.  The Comments section of a Blog (or Document) is not the right vehicle for asking questions as the results are not easily searchable.  Once your issue is solved, a Discussion with the solution (and marked with Correct Answer) makes the results visible to others experiencing a similar problem.  If a blog or document is related, put in a link.  Read the Getting Started documents (link at the top right) including the Rules of Engagement. 

      NOTE: Getting the link is easy enough for both the author and Blog.  Simply MouseOver the item, Right Click, and select Copy Shortcut.  Paste it into your Discussion.  You can also click on the url after pasting.  Click on the A to expand the options and select T (on the right) to Auto-Title the url.

      Thanks, Mike (Moderator)

      SAP Technology RIG

      (0) 
    2. Daniel Silva Post author

      Hi, Óscar.

      As Michael said, please open a separated question and and mark me. I’ll be glad to help you.

      I’d like you to explain a bit more what your problem is and what you are planning to do.

      Regards,

      Daniel

      (0) 
    1. Daniel Silva Post author

      Sorry!

      I’ve just seen your comment. For some reason I was not warned about it. I posted the file content. I hope it helps.

      Regards,

      Daniel

      (0) 
  7. vishnukumarraju kakarlapudi

     

    Hi Daniel,

         i have developed a kapsel push notification cordova based app which is linked to SMP cockpit and i followed this article to develop.

    Android & iOS:

    I’m able to registered with SMP with “Backend” checkbox to “internal”, and were see the APP registered ID in cockpit , push GCM token & able to receive push notificions on device

    Problem :

    1) But in iOS, not able to get registered to SMP with “Backend” ->”internal” option checked, but configuring it to  “Allow Anonymous Access”  making registration successful with smp

    2) Next on triggering the event to PUSH notification registration,  able to see  “tokenID” that has received  from apple in Xcode device console logs, but not showing any alert message for successful registration to push notification.

    3) Pushing  an alert from RestFul client is showing “201” status , but with message

    status”: {

                    “value”: “Unknown push target type”,

                    “code”: 2

                },

    SMP Platform version : SP13

    SMP kapsel version : 3.0.13.3

    Could you please help me  in this, apart from that “ what makes iOS app cockpit registration fails when use with “Backend” -> “Internal” checkbox is checked.

    Best Regards,

    Vishnu.K

    (0) 
  8. vishnukumarraju kakarlapudi

    Hi Daniel,
    Please find the SMP cokcpit logs,

    No logs getting printed after the “No CSI context found in the authentication session. Performing the role check using HttpRequest#”

    #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752007#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target d298b0c4-4ddd-4353-888e-9c1d9ac392bf failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752006#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target 0416a264-0c2d-4984-a2ca-1accaf3c94ce failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752005#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target 7f5a03ac-5ab8-4081-9ab4-27840a5f2c83 failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752004#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target 9589d221-6582-48fd-ba60-e9f1698f69a6 failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752002#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target 4c7455ca-f879-4419-a81f-4de9593f5d49 failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING#Push####1478173628752003#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##PushNotificationDelegator:processNotifications#smppushuser#######750#####Push to target b891d15f-595e-4402-80ce-4b468da977c1 failed. Unsupported notification type null.# #2.0#2016-11-03 05:47:08 AM#WARNING####Security#1478173628752001#7f45b0a8-8e27-46c5-b3a6-fe64a0b44ef2##com.sap.mobile.platform.server.foundation.security.filter.AuthenticationFilter:doFilter#smppushuser#######750#####No CSI context found in the authentication session. Performing the role check using HttpRequest#
    (0) 

Leave a Reply