Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
VILLASweb-backend-go
VILLASweb-backend-go
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ACS
    • P
      Public
  • VILLASframework
  • VILLASweb-backend-goVILLASweb-backend-go
  • Issues
  • #39

Closed
Open
Opened Jul 03, 2020 by Sonja Happ@skolenMaintainer

User Authentication via KeyCloak

User authentication and management via KeyCloak shall be possible. This is a demand from the projects SLEW (teaching project) and ANIM4L (research project).

If possible, the existing user management shall be kept as an alternative solution since it is well suited for small setups of VILLASweb.

The required steps and changes for the KeyCloak integration need to be discussed here. Also, we need to decide who is taking care of the implementation.

@markus.mirz @stvogel

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: acs/public/villas/web-backend-go#39