Errors are not returned when application does not have the required scopes

[arunpassi]

I was trying this sdk to query groups. The Groups().Get() api fails and returns an empty set but err is not set.

       cred, err := azidentity.NewClientSecretCredential(
		<TenandID>,  // Removed for posting here
		<ClientID>,     // Removed for posting here
		<ClientSecret>, // Removed for posting here
		nil,
	)
	if err != nil {
		log.Printf("failed to get cred: %v\n", err)
		return err
	}

	auth, err := a.NewAzureIdentityAuthenticationProviderWithScopes(
		cred,
		[]string{"https://graph.microsoft.com/.default"},
	)
	if err != nil {
		log.Printf("failed to get identity: %v\n", err)
		return err
	}

	adapter, err := msgraphsdk.NewGraphRequestAdapter(auth)
	if err != nil {
		log.Printf("failed to get adapter: %v\n", err)
		return err
	}

	client := msgraphsdk.NewGraphServiceClient(adapter)
	result, err := client.Users().Get(nil)
	if err != nil {
		log.Printf("failed to get users: %v\n", err)
		return err
	}
        client := msgraphsdk.NewGraphServiceClient(adapter)

	resp, err := client.Groups().Get(nil)
	if err != nil {
		log.Printf("failed to get group: %v", err)
		return err
	}
       
       if (len(resp.GetValue()) == 0 {
                log.Printf("failed to get group")
       }

On debugging, I see http request failed with access denied as required scope for querying groups was not present. So error was returned in http request but was not propagated back to the caller.

On adding Directory.Read.All scope, it works fine and I get the groups. Problem is only not getting the error when it should be there.

[baywet]

Hi @arunpassi ,
Thanks for reaching out and trying out the SDK.

You are right, the errors returned by the API are currently not being deserialized, this is a limitation of the generator and I added this to the known limitations list (last point).

Also, looking at your example, you don't need to create a new client for each request, it can be reused. Let me know if you have other questions/concerns.

[arunpassi]

Also, looking at your example, you don't need to create a new client for each request, it can be reused. Let me know if you have other questions/concerns.

Oh yes, that was a copy-paste mistake (pasted that line twice during an overlap).

[baywet]

Thanks. Closing this issue as it's a known limitation we're working on.

[arunpassi]

Hey @baywet , do you have any rough estimate by which this could be resolved?

[baywet]

This one is difficult to estimate since it has multiple layers of dependencies.
We definitively need to tackle it before the general availability of this sdk.
We're targeting a GA around May, but if course that all depends on the feedback we get in this preview as well as other priorities.
Keep using the sdk, the more usage and the more feedback we get, the faster it will GA.

[arunpassi]

@baywet, thanks for the update.