omlie / dat250-group6 Goto Github PK

You can only approve or leave a subscription pending in the current implementation

Using the standard security features of the Java EE framework, implement a working solution for authentication and access control / authorization in the application. This must include a secure login mechanism using password and username, and the solution should use database storage of the user credentials. In the application, there should be at least two different roles with corresponding access rights. Finally, all communication between clients and the server should be protected by using the https protocol.

When a user is approved to use a registered device, the application needs to send a message to a Notify-subsystem implemented as a message-driven bean and the Java Message Service (JMS). You should add a JMS topic to your application in which this information can be published and received by a subscribing message-driven bean. The message-driven bean should sent a message to dweet.io via REST similar to the functionality of the advanced tweet example application.

• getDeviceById(int deviceId) - which should return a representation of the device identified by id

• getSubscribers(int deviceId) - which should return a representation with reference to all current registrations of the device identified by id

• getUserFromSubscriptionId(int deviceId, int registrationId) - which should return a representation of the given rid for the device identified by id

• addSubscription(int deviceId, int userId) - which creates a registration for a specified user for the device identified by id and returns a representation of the registration. The user should be contained in the payload of the request (or optionally as a query parameter).

Also says waiting for approval on owned devices

• Log in
• Add new device
• Add new user
• Search for online devices
• Delete device
• Register for device
• Deregister for device
• See list of devices subscribed to
• Edit owned devices
• Add feedback to devices
• View feedback for owned devices
• Publish device
• Update user data

Don't give the possibility to give feedback if you are not subscribed to a device.

Add endpoints:

• Unsubscribe
• Delete a device
• Edit device
• Approve subscription

• GET /rest/devices - which should return a representation of all devices
• GET /rest/devices/{id} - which should return a representation of the device identified by id
• GET /rest/devices/{id}/registrations/ - which should return a representation with reference to all current registrations of the device identified by id
• GET /rest/devices/{id}/registration/{rid} - which should return a representation of the given rid for the device identified by id
• POST /rest/devices/{id}/ - which creates a registration for a specified user for the device identified by id and returns a representation of the registration. The user should be contained in the payload of the request (or optionally as a query parameter).

We initialize a new user in UserController.getUser() every time, similarly with device.

• An owner should be able to approve/deny pending subscriptions
• You aren't supposed to give feedback if the subscription isn't approved yet
• Devices with pending subscriptions shouldn't be shown in subscribed devices.

• A brief introduction to the software technology that you are investigating (2 slides).
• A summary of what you have done until now and what prototype you are going to build (2 slides).
• A summary of how you intend to proceed in the project and how you will evaluate the prototype (1 slide).

• Log in page
• Session cookie
• Log out

On a device page:

• Subscribe to a device
• Unsubscribe to a device

• Subscribe
• Delete
• Unsubscribe