Java library that integrates to SAP Mobile Services Backend APIs. As a start this will only provide the Notification Backend API to send notifications to mobile devices. Further APIs may be included in the future.

License: Apache License 2.0

Java 100.00%

client integration java mobile-services sap

java-integration-for-sap-mobile-services's Introduction

Java integration for SAP Mobile Services

About this project

Java integration for SAP Mobile Services is a client library to integrate your application with the backend-facing APIs of SAP Mobile Services. As this project only started, it at the moment only provides the integration to the Notification Backend services, which allows you to send push notifications to your mobile devices. Other integrated APIs may be added to this library in the future.

Requirements and Setup

Release	Minimum JDK Version	Spring Boot Version
0.7	JDK 8	2.7
1.x	JDK 17	3.1

See Spring Boot Support for support time frames.

Basic initialization of a PushClient:

MobileServicesSettings mobileServicesSettings = MobileServicesSettings.fromResource("mobileservices.json");
PushClient pushClient = new PushClientBuilder().build(mobileServicesSettings);

Documentation: latest release - dev
JavaDoc: latest release - dev

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2022 SAP SE or an SAP affiliate company and Java integration for SAP Mobile Services contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.

java-integration-for-sap-mobile-services's People

Contributors

Stargazers

Watchers

Forkers

exotrom dirkg68 isabella232 simoncwaterer www-geany-org

java-integration-for-sap-mobile-services's Issues

NotificationStatus Should Include notificationId From BTP Mobile Service Response

The notificationId field comes in handy as soon as Push returns the apns-unique-id to trace notifications

Get Push Registrations

As a message producer, I need to retrieve device registrations, so that I can adopt my messages based on registration details.

The BTP Mobile Services Backend API provides a method to get push registrations by

Registration ID (part of the push response)
By username and/or
By push group

Support x509 service keys for SaaS setup

The current x509 service key implementation is setting the .zoneId() when fetching an XSUAA token 1.
However, in the service key use-case, the XSUAA tenantmode is set to dedicated and not shared, which means the OAuth client does not exist in the subscriber subaccount 2.

The authentication interceptor must be adjusted to use

.zoneId() when tenantmode is set to shared
the provider zoneId + the x-tenant-id header when tenantmode is set to dedicated (or external)

Include API Error Message into Client Exception

When Push Backend API returns a non HTTP-OK status code a HTTP Client Exception is thrown. This should include the Error message from the API

msgType in BaiduNotification is Missing

The Baidu notification payload has three first level properties:

iOS
Android
msgType

The message type is 0 for transparency and 1 for visible notifications

The msgType is missing

How to send APNs attributes that are not mapped by Mobile Services?

Hi everyone,

first of all, thank you for this great library! We have migrated some of our push notification handling to it and it works like a breeze.

However, we encountered a challenge that I could not find a solution for just yet: We would like to send the interruption-level parameter to the APN service along the push notification which is not mapped by Mobile Services. According to the documentation, custom parameters should be sent in a customParameter property to Mobile Services. Unfortunately, it does not seem like this is supported by the library just yet. But also, I could not get this up and running with plain REST. Is there an example how this is supposed to work? If yes, I would happily provide a pull request that adds support for it to this library.

Best regards,
Yannik

Push to multiple Users: Return HTTP-200 if no registration was found

In order to simplify consumption, consider this cases as expected and don't throw exception, but return an empty push message result list

X509 Service Key Support

As a message producer, I want to use X509 Service keys, so that I can benefit from the elevated security by X509 service keys.

The X509 service keys are supported by BTP Mobile Service for a couple of month and documented here SAP Mobile Services Documentation: Service Keys

sap / java-integration-for-sap-mobile-services Goto Github PK