Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
feudalWebpage
feudalWebpage
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • 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
  • feudalWebpagefeudalWebpage
  • Issues
  • #24

Closed
Open
Opened Jun 22, 2020 by lukas.burgey@af9063Owner

Investigate secrets handling

Possible options are:

  • For password: hashes
  • The webpage generates a key pair (and stores it in the local storage) and the client encrypts secret_credentials using the public key (is this possible)
  • Once the webpage local storage is cleared (or the user switches the browser) the user can't access the secret_credential anymore. The user can request a redeployment, which will reencrypt the credentials
Edited Jun 22, 2020 by lukas.burgey
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/feudalWebpage#24