Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

possible rights conflict using device profiles #415

TestingMandy opened this issue Jan 22, 2020 · 1 comment

possible rights conflict using device profiles #415

TestingMandy opened this issue Jan 22, 2020 · 1 comment


Copy link

@TestingMandy TestingMandy commented Jan 22, 2020

Is this a bug or a feature request?


What did you expect?

  • error message on creating the device
  • same behavior of websites and api

What happened?

On creating a new device via api, it is possible to assign a device profile from another organization. Those devices can be created by users, which are admin in serveral organizations.
On creating a device on the server website, device profiles from other organizations are not available in the drop down menu.

Users, that do not know the device profile due to rights are not able to show the detail device webpage. Those devices are listed in the device overview on the server websites, but on clicking on them the login prompt is shown, without any notification or error message for users.

What version are your using?

application-server: 3.6.1

How can your issue be reproduced?

Create a device via api in organization A, but assign a device profile from organization B.
A user, which is only in organization A admin, clicks in device overview on the created device.

Could you share your log output?

@brocaar brocaar closed this in b2142f6 Jan 23, 2020

This comment has been minimized.

Copy link

@brocaar brocaar commented Jan 23, 2020

The above commit fixes this issue (+ adds a test for this).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.