Will need to create the following table structure:
Blocked: #4 (authentication backend)
Permissions
-- Id
-- EnvironmentId
-- ApplicationId
-- UserId
-- Role (1 = ReadSettings, 10 = WriteSettings, 20 = CreateChildApplication, 30 = CreateChildEnvironment) spaced out by 10 allows me to add things like decryptsettings in the future
(NOTE: Think about these queries... this hierarchical data could get quite complex)
Will then need to tap in read/write endpoints to authorize against a new authorization service.
For now this will assume that a user has access to all applications/environments as there is some additional complexity to deal with there. Will do this by creating a test user as part of seed script with all access to root of both.
Will need to create the following table structure: Blocked: #4 (authentication backend)
Will then need to tap in read/write endpoints to authorize against a new authorization service.
For now this will assume that a user has access to all applications/environments as there is some additional complexity to deal with there. Will do this by creating a test user as part of seed script with all access to root of both.