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.

Sign up for GitHub

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

Jump to bottom

Enable AlertSource to be associated with a (system) User. #48

Closed
hmpf opened this issue Jun 11, 2020 · 1 comment · Fixed by #71
Closed

Enable AlertSource to be associated with a (system) User. #48

hmpf opened this issue Jun 11, 2020 · 1 comment · Fixed by #71
Assignees
@ddabble
Labels
discussion Requires developer feedback/discussion before implementation

Comments

@hmpf
Copy link
Contributor

hmpf commented Jun 11, 2020 •
edited by lunkwill42
Loading

For each AlertSource, a User should be created, and the two should be associated. This User should not be able to log in normally through the web interface, but will still be assigned an API token.

This enables the AlertSource to be identified using the API token as it sends events into the API.
@hmpf hmpf changed the title An API pushes on behalf of a system, not a person, have system users? An API pushes on behalf of a system, not a person. Do we need system users? Jun 11, 2020
@hmpf hmpf added the discussion Requires developer feedback/discussion before implementation label Jun 17, 2020
@hmpf hmpf mentioned this issue Jun 17, 2020
Closed
@ddabble
Copy link
Contributor

ddabble commented Jun 18, 2020

Suggestion: Client has to have an auth token to be able to register a system user.

@lunkwill42 lunkwill42 changed the title An API pushes on behalf of a system, not a person. Do we need system users? Enable AlertSource to be associated with a (system) User. Jun 23, 2020
@ddabble ddabble self-assigned this Jun 29, 2020
@ddabble ddabble mentioned this issue Jul 1, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ddabble ddabble

Labels
discussion Requires developer feedback/discussion before implementation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Associate user with AlertSource ddabble/Argus
2 participants
@ddabble @hmpf