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

ListSCIMProvisionedIdentities always returns 404 #2209

Closed
hazcod opened this issue Nov 24, 2021 · 2 comments
Closed

ListSCIMProvisionedIdentities always returns 404 #2209

hazcod opened this issue Nov 24, 2021 · 2 comments

Comments

@hazcod
Copy link

hazcod commented Nov 24, 2021

Hi!

I have an org on github.com with the GitHub Enterprise plan.
I am using v40.0.0 of the library.

	ctx := context.Background()

	ts := oauth2.StaticTokenSource(
		&oauth2.Token{AccessToken: token},
	)
	tc := oauth2.NewClient(ctx, ts)
	tc.Timeout = time.Second * 10

	client := github.NewClient(tc)
	
	resp, err := client.SCIM.ListSCIMProvisionedIdentities(ctx, org, &github.ListSCIMProvisionedIdentitiesOptions{
		StartIndex: nil,
		Count:      nil,
		Filter:     nil,
	})

Wil allways return 404 Not Found. Any idea?
The org matches ironpeakservices, which is my org with SAML SSO enabled.
The token is authorized for the org/SSO.
The token in question has wide scopes: admin:enterprise, admin:org, admin:org_hook, user.

@gmlewis
Copy link
Collaborator

gmlewis commented Nov 24, 2021

I don't have experience with this endpoint, but my first guess was going to be the scopes of your personal access token, which appear to have the ones I would expect.

For cases like these where we get unexpected responses from the GitHub v3 API, one of the best ways to triage it is to generate the identical curl request and see if it returns the same response.

Your best bet is to probably contact GitHub tech support and ask them. Obviously, they would be more interested in seeing the curl version of your request, but if you still get a 404 with the curl version, then they will be the ones that need to help you.

I'll leave this open for a while, but if you hear back, please feel free to report your findings in this issue in order to help others running into the same issue. Thank you!

@gmlewis
Copy link
Collaborator

gmlewis commented Mar 17, 2025

Closing issue due to inactivity.

@gmlewis gmlewis closed this as completed Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants