Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

start work towards enabling launching fuzzing within docker #133

Closed
wants to merge 42 commits into from
Closed

start work towards enabling launching fuzzing within docker #133

wants to merge 42 commits into from

Conversation

bmc-msft
Copy link
Contributor

@bmc-msft bmc-msft commented Oct 12, 2020

Enables launching fuzzing jobs from within a docker container, which will go a long way towards bring-your-own-compute that isn't on Azure.

TODO:

  • - Docker containers can't reboot. Tasks that require rebooting should be rejected from running in containers

@bmc-msft
Copy link
Contributor Author

This PR also lost it's reference back to my fork. Closing and recreating.

@bmc-msft bmc-msft closed this Nov 11, 2020
ghost pushed a commit that referenced this pull request Nov 13, 2020
This PR makes user information from JWT tokens available as part of a Task.

Included changes:
* Renamed `verify_token` to `call_if_agent`, since this function is specific to agent token verification
* Renames `is_authorized` to `is_agent`, since this function checks if the token is an agent
* Adds support for unmanaged nodes in `is_agent` (see #133 for information) 
* Saves the user information from the JWT token on task create as part of `TaskConfig`

Note, `TaskConfig` is what is provided to notification templates.  This enables Github issues and ADO work items to tie back to the user that created the task.

Note, while `upn` _usually_ means email for AAD user tokens.  If we were going to make use of the email address, we should perform a graph lookup based on the `oid`, but we're not.
@ghost ghost locked as resolved and limited conversation to collaborators Apr 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants