Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Unsupported OIDC Scopes #1023

Open
3 tasks done
spyr0-sec opened this issue Dec 17, 2024 · 0 comments
Open
3 tasks done

Bug: Unsupported OIDC Scopes #1023

spyr0-sec opened this issue Dec 17, 2024 · 0 comments
Labels
bug Something isn't working triage This issue requires triaging

Comments

@spyr0-sec
Copy link
Contributor

Description:

The static OIDC configuration contains scopes which are not supported by EntraID and other identity providers

Are you intending to fix this bug?

No

Component(s) Affected:

  • UI
  • API

Steps to Reproduce:

  1. Settings
  2. Administration
  3. SSO Configuration
  4. Configure SSO Provider

Expected Behavior:

The identity provider is correctly configured for SSO

Actual Behavior:

The Oauth config includes scopes which are not supported and therefore returns error messages

Screenshots/Code Snippets/Sample Files:

https://github.com/SpecterOps/BloodHound/blob/v6.3.0/cmd/api/src/api/v2/auth/oidc.go#L109

Environment Information:

BloodHound: v6.3.0

Additional Information:

For our identity provider, only "openid", "profile", "email" are supported.

As per slack thread, EntraID is complaining about the email_verified scope

Potential Solution (optional):

Make the configuration more customisable with the ability to select which scopes are required for the given IdP

Related Issues:

N/A

Contributor Checklist:

  • I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
  • I have provided clear steps to reproduce the issue.
  • I have included relevant environment information details.
@spyr0-sec spyr0-sec added bug Something isn't working triage This issue requires triaging labels Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This issue requires triaging
Projects
None yet
Development

No branches or pull requests

1 participant