Add: validate source names in CREATE_USER and MODIFY_USER

[mattmundell]

What

Validate the auth method names that are passed to CREATE_USER and MODIFY_USER in SOURCES/SOURCE.

Why

Doing the validation is cleaner and safer because it restricts which strings end up in users.method in the db.

Example

Before this PR you could add a user with a bogus SOURCE:

$ o m m '<create_user><name>test1</name><password>test</password><sources><source>xxx</source></sources></create_user>'
<create_user_response status="201" status_text="OK, resource created" id="16751142-63b6-44bd-9f41-7559dc50d5e8"/>

and the xxx would be stored in the db:

$ o m m '<get_users user_id="16751142-63b6-44bd-9f41-7559dc50d5e8"/>'
<get_users_response status="200" status_text="OK">
  <user id="16751142-63b6-44bd-9f41-7559dc50d5e8">
    <sources>
      <source>xxx</source>
    </sources>

After the PR:

$ o m m '<create_user><name>test2</name><password>test</password><sources><source>xxx</source></sources></create_user>'
<create_user_response status="400" status_text="Error in SOURCE" />

Similar for MODIFY_USER:

$ o m m '<modify_user><name>test2</name><password modify="0"/><sources><source>yyy</source></sources></modify_user>'
<modify_user_response status="400" status_text="Error in SOURCES" />

References

Requires greenbone/gvm-libs/pull/819.

Resolves a TODO added in aacc589 in 2013.

[github-actions]

Conventional Commits Report

Type	Number
Added	1

🚀 Conventional commits found.