steveej/msc-thesis
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases 4 Packages Wiki Activity Actions

Define use-cases to derive authorization requirements for the container infrastructure #4

New issue
Closed
opened 2015-11-14 00:40:56 +00:00 by steveej · 0 comments
steveej commented 2015-11-14 00:40:56 +00:00 (Migrated from gitlab.com)
Copy link

Define authorization use-cases for the following scenarios

  • university infrastructure
  • self-hosting software development company infrastructure
Define authorization use-cases for the following scenarios - [ ] university infrastructure - [ ] self-hosting software development company infrastructure
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
static-code-analysis-kernel-task-memory-safety
package-centric-containers
ideal-distributed-architecture
1.0.1
1.0.0
0.2.1-alpha
0.2.0-alpha
Labels
Clear labels   
Doing

   
To Do

   
basic

   
bug

   
duplicate

   
enhancement

   
evaluation

   
help wanted

   
invalid

   
priority/High

   
priority/Normal

   
research

   
topic/ideal-distributed-infrastructure

   
topic/package-centric-containers

   
type/Backlog

   
type/Planned

   
wontfix
No labels
Doing
To Do
basic
bug
duplicate
enhancement
evaluation
help wanted
invalid
priority/High
priority/Normal
research
topic/ideal-distributed-infrastructure
topic/package-centric-containers
type/Backlog
type/Planned
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: steveej/msc-thesis#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?