Page Comparison

For the slide deck on RBAC and implementation design, please check out - https://docs.google.com/presentation/d/1wNp1re47Isc_BX_wZWPjmJkOgnSqrlfhiNKRqJrirFE/edit#slide=id.p

...

edit?usp=sharing

Design:

• Use OPA and Envoy as sidecars in backend microservices for authorization

• A program which can convert the json schema definitions to OPA rego code

• Sample schema definition (Work in progress, but the design is more or less as it looks below, some parts of the json keys can change to make more meaningful naming convention)

Schema in YAML

• Token structure

---{
- name: createContent
  uris "aud": "/content/v1/create"
  upstream_url: http://knowledge-mw:5000/v1/content/create
  role_check:
    config.allowed_roles:
    - CONTENT_CREATOR
    - COURSE_CREATOR
  org_check:
    config.look_in:
    - body
    - header
    config.operator: and
    config.body: request.content.createdFor[*]
    config.header: X-Org-Id
  owner_check:
    config.look_in:
    - header
    config.header: X-User-Id

Schema in JSON

[
  {
    "name": "createContenthttps://sunbirded.org/auth/realms/sunbird",
  "sub": "f:229738b7-253c-4adf-9673-a857ppb86999:gca2925f-1qqq-4654-9177-fece3fd6afc9",
  "roles": [
    {
      "role": "BOOK_CREATOR",
      "scope": [
        {
          "organisationId": "0127134797703392110"
        }
      ]
    },
    {
      "role": "CONTENT_CREATOR",
      "urisscope": "/content/v1/create", [
     "upstream_url": "http://knowledge-mw:5000/v1/content/create",  {
  "role_check": {       "config.allowed_rolesorganisationId": [
        "CONTENT_CREATOR","0127134797703392110"
        "COURSE_CREATOR"}
      ]
    },
    "org_check": {
      "config.look_inrole": [
 "CONTENT_REVIEWER",
      "bodyscope",: [
       "header"   {
   ],       "config.operatororganisationId": "and0127134797703392110",
      "config.body": "request.content.createdFor[*]",
 }
     "config.header": "X-Org-Id" ]
    },
    "owner_check{
      "role": {"COURSE_MENTOR",
      "config.look_inscope": [
        "header"{
      ],       "config.header"organisationId": "X-User-Id0127134797703392110"
    }    }
]

• Schema can use the config.operator or can omit. The config.operator takes and or values which signify AND and ORoperation. If AND is used, then both keys are checked against the token and both need to match, if OR is used, then one of the key should match in the token

• For a given check, the schema will not allow both AND OR operation to be used (example a && b || c). These type of checks will be treated as custom checks and will be directly implemented in rego. But these will work aa || bb || cc , aa && bb && cc

• Sample token structure

{   "aud": "https://demo.sunbirded.org/auth/realms/sunbird",   "sub": "f:979738b7-253c-4adf-9673-a857eeb86115:fca2925f-1eee-4654-9177-fece3fd6afc9",]
   "roles": [ },
    {
      "role": "BOOKORG_CREATORMODERATOR",
      "scope": [
        {
          "organisationId": "012698787975036928100127134797703392110"
        }
      ]
    },
    {
      "role": "CONTENTPROGRAM_CREATORDESIGNER",
      "scope": [
        {
          "organisationId": "012698787975036928100127134797703392110"
    
   }       ]
    },
    {       "role": "CONTENT_REVIEWER",
      "scope": [
        {
          "organisationId": "012698787975036928100127134797703392110"
        }
      ]
    },
    {
      "role": "COURSEREPORT_MENTORADMIN",
      "scope": [
        {
          "organisationId": "012698787975036928100127134797703392110"
        }
      ]
    },
    {
      "role": "PROGRAM_DESIGNERPUBLIC",
      "scope": [
        {
          "organisationId": "0130107621805015068"
        }
      ]
    }
  ],
  "iss": "https://demo.sunbirded.org/auth/realms/sunbird",
  "name": "Demo",
  "typ": "Bearer",
  "exp": 16379065331640408569,
  "iat": 16378201341640322173
}

...

• Addminutils will invoke the get user roles API and append the roles and orgs information to JWT token, sign it and then issue it to the user

...

New

...

flow on Portal and Mobile for anonymous and logged sessions

...

• The portal and mobile both will do a recaptcha check and pass the recaptcha response to backend for verification (portal backend in case of portal, android recapthca check in case of mobile)

• Once recaptcha response is verified, an API call is made for anonymous session to fetch a token for the user

• As of now we will allow only the portal and mobile app to invoke these register APIs on behalf of the user. The register API is protected by a JWT token that is injected only in mobile and portal

• These tokens (which are issued to portal and mobile on behalf of the user) will have a higher rate limit (maybe 500 per hour)

• A anonymous user can also directly obtain a token, how to do that is mentioned somewhere below in this post, but such token will have a very low ratelimit (maybe like 100 per hour)

• Kong ACL’s will be removed as we will not require any ACL checks, the API authroriztion check will be handled by OPA and Envoy sidecars

...

• Any external system that requires access to API’s, can sigup as an user on Sunbird and then use one of the mentioned flows to generate access token

• API access as usual will be based on the role of the user account on Sunbird

• Any special API access can be granted by Sunbird admin by assigning the appropriate roles on the system

• If the external system requires user context API’s for other users, then they can authenticate on Sunbird as the user and then use the user specific token for any use cases involved in their end (similar to VDN authentication)

• We can also have a button on the portal UI to get the access token after login (similar to the ops support tool)

...

External systems can obtain a token as anonymous

...