Role based access control / backend

[Haarolean]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[Haarolean]

Roles file example:

- name: "memelords"
  clusters:
    - dev
    - staging
    - prod
  subjects:
    - provider: oauth_google
      type: domain
      value: "memelord.lol"
    - provider: oauth_google
      type: user
      value: "[email protected]"

    - provider: oauth_github
      type: organization
      value: "memelords_team"
    - provider: oauth_github
      type: user
      value: "Haarolean"
  permissions:
    - resource: cluster
      name: ".*" 
      actions: [ "view", "create" ]

    - resource: topic
      actions: [ "view", "create", "edit" ]
      name: ".*" 

    - resource: connect
      actions: [ ".*" ]
      name: ".*" 

# not implemented yet
#      selector:
#        connector:
#          name: ".*"
#          class: 'com.provectus.connectorName'

- name: "admins"
  clusters:
    - dev
    - staging
    - prod
  subjects:
    - provider: ldap
      type: group
      value: "ou=devs,dc=planetexpress,dc=com"
    - provider: ldap
      type: user
      value: "cn=germanosin,dc=planetexpress,dc=com"
  permissions:
    - resource: cluster
      actions: [ "view" ]
      name: ".*" 

API response example:

[
  {
    "resource": "cluster",
    "value": "local",
    "actions": [
      "view",
      "edit"
    ]
  },
  {
    "resource": "topic",
    "value": "first.messages",
    "actions": [
      "view",
      "create"
    ]
  }
]

[iliax]

lgtm, minor comments left

fixed comments

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
11 Code Smells

89.8% Coverage
0.0% Duplication