SpecterOps / SpecterOps/GitHound

Handle Entra ID federated identities

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
146
Forks
18
No merged PRs in 30d

Description

One of the way a workflow can be authenticated on EntraID/Azure is by using OIDC and federated identities.

Image

This make sense for GitHound and BloodHound to make this connection, as a Service Principal on Entra can be linked to a GitHub repositories.

Reference:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Azure OIDC workflow examples and the linked Microsoft Entra reference to understand the requested federated-identity connection. Then inspect GitHound's existing authentication entry points; done should be defined as a working Entra ID connection for a GitHub repository, but the issue does not identify files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, github-actions, powershell
Domain
authentication, cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.