Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 216
    • Issues 216
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #329

Closed
Open
Created Jun 24, 2020 by Marcin Siodelski@marcinMaintainer

Enable authentication for the traffic generators

Now that we have fixed a bug that allowed for unauthorized access to some Stork views we need to modify the DHCP and DNS traffic generators to create the session (login) prior to getting configured DHCP subnets from the server. Without this, the traffic generators fail t get the list of subnets and this makes them unusable.

The useful reference I got from @godfryd was: https://requests.readthedocs.io/en/master/user/advanced/

Assignee
Assign to
Time tracking