Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
feudalBackend
feudalBackend
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • feudal
  • feudalBackendfeudalBackend
  • Issues
  • #6

Closed
Open
Opened Oct 25, 2018 by marcus.hardt@lo0018Owner2 of 3 tasks completed2/3 tasks

Undeployment Concept

Drei Use Cases:

  • Nutzer fliegt aus VO
  • Nutzer fliegt aus IdP
  • Nutzer wird zentral suspended

In alled drei Fällen muss der Nutzer undeployed werden. Evtl. muss auch noch ein "suspend" target definiert werden.

Wichtig wäre, erstmal ein Konzept zu haben, wie FEUDAL die Infos mitbekommt und darauf reagiert.

Edited Jan 17, 2019 by ubedv
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: feudal/feudalBackend#6