Resolve "Implement integration tests for RBAC"

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Related to #340

added goSDN priorityhigh statusongoing typeimprovement labels

assigned to @hda11249

added 1 commit

• ebbdc129 - started adding user creation and modification test, not working

Compare with previous version

added 7 commits

• ebbdc129...034136a5 - 6 commits from branch master
• 485b1a8f - Merge branch 'master' into 340-implement-integration-tests-for-rbac

Compare with previous version

added 2 commits

• 9e4b9f9e - fixed issue with user creation, fixed user creation and modification test, added note in suer proto
• c42bcc54 - changed visibility of function in utility, added test for user permission checking, fails currently

Compare with previous version

added 1 commit

• ca52723a - fixed permission test not failing anymore

Compare with previous version

added 1 commit

• 29c15a14 - remove rogue comment

Compare with previous version

added 1 commit

• 4f73ff08 - added cleanup utility for users and roles, reverted small workaround in test

Compare with previous version

added 1 commit

• 8577ca91 - added option to add role with id, add role adding and manipulation tests

Compare with previous version

added 9 commits

• 8577ca91...fcf28de9 - 8 commits from branch master
• e70ef2c4 - Merge branch 'master' into 340-implement-integration-tests-for-rbac

Compare with previous version

General question, where do we put tests like is this user allowed to access this devices? Should it go into rbac or device tests? My first idea would be to put them into the rbac tests.

requested review from @neil.schark

added 4 commits

• c9ca79c1 - move rbac utils to general utils
• 5d4ff8d4 - make gettimestamp public
• ab3e34e2 - change panics, add additional cleaning in beginning of the test
• b0962d83 - used assert package for test assertion

Compare with previous version

added 1 commit

• 9632f43c - move const to top of file

Compare with previous version

marked this merge request as ready