- Posts: 5
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- when the user logs in (through the jbackend api)... the next services yo call (ie. register push device token) come along with cookie based authentication or you need to pass the session_id somehow?
- when the push token from the device is registered, does jbackend assigns the user to the device?
- can a user have multiple devices assigned?
- what happens if the same device if used by multiple users? (dos jbackend update the relation device-user?)
- how to set up a scheduled job to call the push scheduler?
- is there a way from the device to get all notifications sent to it? can they be filtered by state?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- I assume we need to set up a scheduled job that calls "Push / Scheduler" API end point. Is that correct?
- When you send a notification, the jbackend push module connects to APNS and/or GCM and send it to the devices matching the user/groups. Also I assume jbackend creates an entity "notification" in the database. If that is so, is there an endpoint in the API to get those notification entities from the datase with some kind of filter (user/group)?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- Having the "session id" option enabled, the cookie based authentication still works.
- Don't know how to pass the session_id parameter to other service endpoints ie "user profile" ({{basepath}}/index.php?option=com_jbackend&action=get&module=user&resource=profile)
- login using JSON not working ({{basepath}}/index.php?option=com_jbackend&action=post&module=user&resource=login) + JSON body
Please Log in or Create an account to join the conversation.