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

ALM API does not automatically trust a SharePoint-hosted app on installing to a site #1172

Closed
DanyWyss opened this Issue Dec 21, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@DanyWyss

DanyWyss commented Dec 21, 2017

Category

  • [X ] Bug

Expected or Desired Behavior

When installing a SharePoint-hosted Add-In from the app catalog the app should be trusted on the site collection automatically.

Observed Behavior

After installing the SharePoint-hosted Add-In with site collection scoped permissions the app is deployed to the provided site but not trusted. Trust has to be done manually through the SharePoint UI which destroys the whole purpose of fully automating provisioning of apps using ALM API.

Steps to Reproduce

Prerequisites:

Using ALM API from PnP Powershell (but can be reproduced in any other way of using SharePoint ALM API):

  • Connect to site: Connect-PnPOnline –Url https://yourtenant.sharepoint.com/sites/yoursite
  • Find out the app's Id using: Get-PnpApp
  • Install app to site: Install-PnPApp -Identity <AppId> (where is Id as listed in Get-PnPApp)
  • Go to SharePoint site in browser, navigate to Site Contents and look for installed/installing app
  • Wait until app is fully installed
  • Click on the app to open it's main page
    You'll get the following error "Access denied: You don't have enough permissions or you don't trust this app." is shown.

To manually trust (which shouldn't be necessary): Go to Site Contents and select "Manage permissions" in the "…" menu for the appropriate app, then click the "here" link in the text "If there's something wrong with the app's permissions, click here to trust it again."

@VesaJuvonen

This comment has been minimized.

Show comment
Hide comment
@VesaJuvonen

VesaJuvonen Dec 28, 2017

Contributor

Hi @DanyWyss, this has been identified now and we should have it now fixed. We'll test this in following days and hopefully, we can push out the fix to production early January. Really unfortunate one, but we are working on getting it resolved asap.

Contributor

VesaJuvonen commented Dec 28, 2017

Hi @DanyWyss, this has been identified now and we should have it now fixed. We'll test this in following days and hopefully, we can push out the fix to production early January. Really unfortunate one, but we are working on getting it resolved asap.

@DanyWyss

This comment has been minimized.

Show comment
Hide comment
@DanyWyss

DanyWyss Jan 3, 2018

Hi @VesaJuvonen, great news, can test as soon as the fix is available. Thanks!

DanyWyss commented Jan 3, 2018

Hi @VesaJuvonen, great news, can test as soon as the fix is available. Thanks!

@VesaJuvonen

This comment has been minimized.

Show comment
Hide comment
@VesaJuvonen

VesaJuvonen Feb 3, 2018

Contributor

Sorry for the delay around this. We had some complications with the fix but should have now things again worked out. We will finalize testing early next week and roll out the fix to production asap based on those results. I'll update and close this issue when things have been verified and 100% rolled out to production.

Contributor

VesaJuvonen commented Feb 3, 2018

Sorry for the delay around this. We had some complications with the fix but should have now things again worked out. We will finalize testing early next week and roll out the fix to production asap based on those results. I'll update and close this issue when things have been verified and 100% rolled out to production.

@VesaJuvonen

This comment has been minimized.

Show comment
Hide comment
@VesaJuvonen

VesaJuvonen Mar 15, 2018

Contributor

Fix has been now rolled out to production. We do apology delay around this, but the issue is finally fixed. Issue was related on the add-ins and did not include SPFx solutions. Closing this as root cause has been now fixed.

Contributor

VesaJuvonen commented Mar 15, 2018

Fix has been now rolled out to production. We do apology delay around this, but the issue is finally fixed. Issue was related on the add-ins and did not include SPFx solutions. Closing this as root cause has been now fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment