add views relating to auth and OAuth

[mattlub]

high priority:

• [x] login (GET /login)
• [x] register (GET /register)
  • check the User model for required fields
• [x] authorise app (GET /oauth/authorize)
  • query params client_id, redirect_uri, state (iirc- check them)
  • renders page specific to the client (app)

lower priority:

• [ ] register app (GET /oauth/register-app)
  • requires authentication
  • check the Client model for required fields
• [ ] my apps
  • requires authentication

@des-des @m4v15 thoughts on the endpoints I've suggested?

[m4v15]

@JWLD @mattlub Just wanted to make you aware that currently, the post request to /register expects a particular kind of body, like this:

    const { englishName, arabicName, email, username, imageUrl } = req.body
    const en = englishName && { name: englishName }
    const ar = arabicName && { name: arabicName }
    return Users.create(Object.assign(
      {
        username: username,
        password: passwordHash,
        role: roles.BASIC,
        email: email,
        imageUrl: imageUrl
      },
      { ar },
      { en }
    ))

we can allow for organisation name as englishOrgNam and arabicOrgName (didn't do it originally but am going to do it before the PR is finished

[m4v15]

Those endpoints look good to me - you know what each form is POST ing to as well yeah?

[m4v15]

Are we going to get rid of the user endpoints on the API?

Or I guess we always said we'd just secure these for only SUPER

[des-des]

@mattlub they look good.

[des-des]

scope done for this sprint