Create "App" Schema/CRUD then Link API Keys and Roles

[nelsonic]

While preparing to create the function that returns the List of Roles for an App https://github.com/dwyl/rbac/issues/3,
I noted that we don't actually have the concept of different "Applications" in Auth right now ... 🙄
Our original idea for the Auth API Key #42 was to allow people to run the DWYL App on their localhost without having to setup an Auth server. That goal was achieved. ✅
However if we want Auth to be a turnkey multi-app auth solution, we need the concept of "Apps".

Gonna transfer a few of the fields over from the API key specifically:

• name
• description
• url
• person_id

auth/lib/auth/apikey.ex

Lines 9 to 16 in fafc5e0

	schema "apikeys" do
	field :client_secret, :binary
	field :client_id, :binary
	field :description, :string
	field :name, :string
	field :url, :binary
	field :person_id, :id
	field :status, :id

Todo

• Create App schema

  • belongs_to person
  • name
  • description
  • url
  • status
  • has_many apikeys

• Migrate data from API Key to App

• Update apikeys schema to have a belongs_to so the app owns the key.

Once this is done we will need to:

• add app_id to Roles so that we can have distinct roles for different applications
  and can create unlimited Apps/Roles. Add app_id to roles schema #108

  Note: no need for a migration on this, just edit the original Roles create migration/schema as it's all part of the same PR PR: RBAC Role Based Access Control #27 #31 #82 #85

• Add app_id to Roles table in /people (index view) and /people/:id

[nelsonic]

After reading through the code that creates API keys, I've realised that it's a bit more work than T1h so I have revised up my estimate. I think think this feature and the corresponding refactor/rework will take me a day. It's at least a couple of hundred lines of code and tests need to be updated/re-written too ... ⏳

[nelsonic]

mix phx.gen.html Ctx App apps person_id:references:people name:binary description:binary url:binary status:references:status apikey_id:references:api end:naive_datetime

Default UI for creating an App:

Obviously this UI is hideous so I'm going to tidy it up.

[nelsonic]

The "end" field is not relevant for now, so this is what the /apps/new form looks like:

[nelsonic]

This issue is complete. #85