Hi Everybody,

I have a provider hosted app on my SharePoint environment. The app is working fine and loads a form.

Within the form there are two client side SharePoint controls. One managed property and one people picker.

For both of these controls when I try to click on them and insert the value I get below client side error message in my browser console and nor term set not people picker works and loads value:

There is no trusted URLs configured for the app deployment

Also in the ULS log I see this error message (not sure wether it's related to the above issue or not):

SPJsonWebSecurityBaseTokenHandler: ValidateActorlsSelfIssuer! Issuer 'XXXXXXXX' is not self issuer.Any idea on why I could not get these two controls working on my provider hosted app?

Regards,

• Edited by Parmo Sunday, April 26, 2015 12:08 AM

Hi Murugesa,

Certificate settings have been done by admin, I would say no I'm not sure.

when I try to run this command I get :

New-SPTrustedSecurityTokenIssuer : The trusted provider certificate already
exists.
At line:1 char:1
+ New-SPTrustedSecurityTokenIssuer -Name "High Trust Cert2" -Certificate
$certific ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...rityTokenIssuer:
   SPCmdletNewTrustedSecurityTokenIssuer) [New-SPTrustedSecurityTokenIssuer],
   InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewTrust
   edSecurityTokenIssuer

How can I make sure those settings are right?

• Edited by Parmo Sunday, April 26, 2015 4:54 AM

all the commands which I tried to run:

$publicCertPath = "C:\Certs\xxxxx.cer"
$certificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($publicCertPath)
New-SPTrustedRootAuthority -Name "yyyyy" -Certificate $certificate
$realm = Get-SPAuthenticationRealm
$specificIssuerId = "11111111-1111-1111-1111-111111111111"
$fullIssuerIdentifier = $specificIssuerId + '@' + $realm
New-SPTrustedSecurityTokenIssuer -Name "High Trust Cert2" -Certificate $certificate -RegisteredIssuerName $fullIssuerIdentifier IsTrustBroker
iisreset

• Edited by Parmo Sunday, April 26, 2015 4:51 AM

Hi, Thanks for the reply.

I'm deploying the app through app catalogue.

I've also created another client id and secret id for the app but got to the same point with no change.

• Edited by Parmo Sunday, April 26, 2015 11:41 PM

I've got everything on one single server.

Everything is on-premise.

here is the code.

 $.getScript(scriptbase + 'SP.Runtime.js',
        function () {
            $.getScript(scriptbase + 'SP.js',
                function () {
                    $.getScript(scriptbase + 'SP.RequestExecutor.js', function () {
                       context = new SP.ClientContext(Office.Samples.PeoplePickerBasic.appWebUrl.toLowerCase());
                        var factory = new SP.ProxyWebRequestExecutorFactory(Office.Samples.PeoplePickerBasic.appWebUrl.toLowerCase());
                        context.set_webRequestExecutorFactory(factory);
                        $.getScript("../Scripts/PeoplePicker/Office.Controls.js", createControl);
                    });

                     $.getScript(scriptbase + 'init.js',
                        function () {
                            $.getScript(scriptbase + 'sp.taxonomy.js');
                        });
                });
        });

• Edited by Parmo Tuesday, April 28, 2015 3:59 AM

Hi,

You cannot access this as its designed to access the content from App.

Can you please tell us what permission has been used on your app ? User only permissions or User+App permission

May be you do not have access permission on the App.

this is what I have used:

  <AppPermissionRequests AllowAppOnlyPolicy="true">

Hi,

Ensure your app permission for Use rProfile and Taxonomy too.

Hi,

All sorted and fixed by reinstallation of certificate authority, issuer and assigning new client ids and secret ids to app.

Another problem was also with app registration in sharepoint (app domain was configured wrong)

Thanks for the help.

Regards,

Hi Parmo,

This is the root cause ( App Development on your on-premise is not been configured correctly) for all your app problem, 

Please follow  any of these link and ensure all the steps are fulfilled.

App environment settings on on-premise -1

App environment settings on on-premise -2

App environment settings on on-premise -3