Sp-dev-docs: Cannot approve apps permission on my api management

[komzy96]

im trying to use a webpart i downloaded from github but im having issues with the api management. Can you help resolve this.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[VesaJuvonen]

Hi @komzy96, can you share the tenant name using a private message either using LinkedIn, TechCommunity or Twitter, so that we can have a closer look on this. We are getting few of these now, so curious on checking exact details from the server side logs. Thx.

[komzy96]

Can I share the tenant here via mail or kindly share your linkedin profile.
Warm regards

On Tue, Jan 21, 2020, 3:13 PM Vesa Juvonen [e-mail] wrote:

Hi @komzy96 https://github.com/komzy96, can you share the tenant name
using a private message either using LinkedIn, TechCommunity or Twitter, so
that we can have a closer look on this. We are getting few of these now, so
curious on checking exact details from the server side logs. Thx.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQONGBA7BKIGBKERCZQTQ637KBA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJP334I#issuecomment-576699889,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOMR7RKWJLWR4KWCMGDQ637KBANCNFSM4KJSR5MQ
.

[komzy96]

Or your Twitter handle I'll be willing to share any information you want

Kind Regards.

On Tue, Jan 21, 2020, 4:08 PM ekomobong willie [e-mail] wrote:

Can I share the tenant here via mail or kindly share your linkedin profile.
Warm regards

On Tue, Jan 21, 2020, 3:13 PM Vesa Juvonen [e-mail]
wrote:

Hi @komzy96 https://github.com/komzy96, can you share the tenant name
using a private message either using LinkedIn, TechCommunity or Twitter, so
that we can have a closer look on this. We are getting few of these now, so
curious on checking exact details from the server side logs. Thx.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQONGBA7BKIGBKERCZQTQ637KBA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJP334I#issuecomment-576699889,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOMR7RKWJLWR4KWCMGDQ637KBANCNFSM4KJSR5MQ
.

[VesaJuvonen]

@komzy96 - LinkedIn profile would be following - https://www.linkedin.com/in/vesajuvonen/ - most likely easiest. Just send message there. Thx.

[komzy96]

Can't send you a message on LinkedIn cause I don't have the premium version.
Can you share your email address?

On Tue, Jan 21, 2020, 4:10 PM Vesa Juvonen [e-mail] wrote:

@komzy96 https://github.com/komzy96 - LinkedIn profile would be
following - https://www.linkedin.com/in/vesajuvonen/ - most likely
easiest. Just send message there. Thx.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQOOPLNIJJUJM3RKVVMDQ64F5PA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQCELI#issuecomment-576725549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOIGT6DTUMS6XDUOLXTQ64F5PANCNFSM4KJSR5MQ
.

[komzy96]

Although I just connected with you as Willie ekomobong please accept the
connection.

On Tue, Jan 21, 2020, 4:30 PM ekomobong willie [e-mail] wrote:

Can't send you a message on LinkedIn cause I don't have the premium
version.
Can you share your email address?

On Tue, Jan 21, 2020, 4:10 PM Vesa Juvonen [e-mail]
wrote:

@komzy96 https://github.com/komzy96 - LinkedIn profile would be
following - https://www.linkedin.com/in/vesajuvonen/ - most likely
easiest. Just send message there. Thx.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQOOPLNIJJUJM3RKVVMDQ64F5PA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQCELI#issuecomment-576725549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOIGT6DTUMS6XDUOLXTQ64F5PANCNFSM4KJSR5MQ
.

[JarbasHorst]

It is not the same kind of error, but it would be interesting to see if the error persists when changing the resource from Microsoft Graph to Microsoft.Azure.AgregatorService in the package-solution.json. I've found it in this documentation here: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aad-tutorial#deploy-the-solution-and-grant-permissions

I hope it helps!

[komzy96]

Thanks jarbas I'll quickly try this out although the error I'm have is HTTP
500 rather than HTTP 400. I'll update soon on my results.
Kind regards.

On Tue, Jan 21, 2020, 4:43 PM Jarbas Horst [e-mail] wrote:

It is not the same kind of error, but it would be interesting to see if
the error persists when changing the resource from Microsoft Graph to
Microsoft.Azure.AgregatorService in the package-solution.json. I've found
it in this documentation here:
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aad-tutorial#deploy-the-solution-and-grant-permissions

I hope it helps!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQOKFC6B3HPW7UNFURYDQ64J27A5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQGDQI#issuecomment-576741825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOM3SSS6BCMHDSS6HSDQ64J27ANCNFSM4KJSR5MQ
.

[VesaJuvonen]

@komzy96 - was actually able to trace this with the GUID from the pic. Seems like a permission issue. Is the account which you are using tenant administrator as the logs would suggest otherwise, so would double check that first. Can you please confirm this as it helps on the trouble shooting - thx.

[komzy96]

The account is just a SharePoint administrator for the tenant but not a
global administrator for the tenant.

On Tue, Jan 21, 2020, 5:27 PM Vesa Juvonen [e-mail] wrote:

@komzy96 https://github.com/komzy96 - was actually able to trace this
with the GUID from the pic. Seems like a permission issue. Is the account
which you are using tenant administrator as the logs would suggest
otherwise, so would double check that first. Can you please confirm this as
it helps on the trouble shooting - thx.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQOKCZZA36KJRULPIJHLQ64PAZA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQLJOY#issuecomment-576763067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOKQTBMVIPQAZPXKZILQ64PAZANCNFSM4KJSR5MQ
.

[VesaJuvonen]

and that's the problem in this case. Behind of the scenes you are actually approving tenant admin operations in Azure AD, which then a SharePoint admin account does not have the permissions... as by default that would not be the case. This then throws an ugly exception which we at the Microsoft need to make more informative.

We should actually check that the user who arrives on the API management page has the sufficient permissions and if that's not the case, we should have clear and informative message around the required permissions.

So - in short - Your exception is as expected you'll need to be tenant administrator to approve the API permissions.

[komzy96]

Okay. I'll inform the global administrator to approve the requests and get
back to you with the feedbacks.
Thanks for your time.

On Tue, Jan 21, 2020, 5:51 PM Vesa Juvonen [e-mail] wrote:

and that's the problem in this case. Behind of the scenes you are actually
approving tenant admin operations in Azure AD, which then a SharePoint
admin account does not have the permissions... as by default that would not
be the case. This then throws an ugly exception which we at the Microsoft
need to make more informative.

We should actually check that the user who arrives on the API management
page has the sufficient permissions and if that's not the case, we should
have clear and informative message around the required permissions.

So - in short - Your exception is as expected you'll need to be tenant
administrator to approve the API permissions.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/5184?email_source=notifications&email_token=ALSEQOJT7ILUKBFZ3RXDLDDQ64RYXA5CNFSM4KJSR5M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQN6RA#issuecomment-576773956,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSEQOIGE66Y6MKRBA25EZTQ64RYXANCNFSM4KJSR5MQ
.

[komzy96]

Hey vesa you where right. the issue has been fixed. Thanks

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues