developing a provider hosted application where the application redirects to different pages of a web application hosted on an azure web site.
This web site also handles the app installed event.
The problem is that in the web.config of the site, we need to add a client ID and Password, but these (Client ID/Password) are automatically generated by the SharePoint Online app registration page, after we register the application on the SharePoint online site.
So if we install the app on this SPOnline Site , it works fine, but if we try to install it on another site, when it redirects to the azure web site page, we got an authentication error.
need to add a unique client ID and password to the azure web site so when the SharePoint app in being installed on any Client ‘s SharePoint site can be identified as safe, authenticated and well-functioning with the azure site.
In the current process, we have to create an azure web site for each SharePoint Site where the application is being installed
How is this done with SharePoint plugins? Does the provider have to generate the Id and secret on each SharePoint Site.
In the SharePoint web provider project code , I found something called HostedAppSigningKey and HostedAppName , but did not find any tutorial about that. Can these be used for a solution?
To support multiple environments you should generate a id/secret from the Microsoft Seller Dashboard (even if you don't plan to sell your add-in) and use one set for all the environments. You should not use the appregnew page.
Related
I have created a provider-hosted app which was developed and tested against SharePoint Online. I now want to install this on SharePoint 2013 On Premise.
It is my intention that, despite being a provider hosted app, I wish to host the app web in IIS on the SharePoint server (single farm not a cluster). I then intend to use a local URL for my App Web URL.
I understand the process of setting up an App Catalog (On SharePoint Online) as a repository for my App which in turn will enable users to add it to a site.
I have only been able to find a guide to setup On Premise SharePoint to allow users to use the SharePoint store but I only want to set it up for third party apps.
My question is do I need to go through all the steps in this link https://technet.microsoft.com/en-gb/library/fp161236.aspx even if I don't want/require store access? I don't not want to do more than necessary and I would prefer a simple solution for my clients.
I followed this guide https://technet.microsoft.com/en-gb/library/fp161234.aspx in the hope that creating the app catalog would be sufficient but I get the error "Sorry, apps are turned off. If you know who runs the server, tell them to enable apps."
We use Azure.
We have a web application, an admin site, and also an Web API (for mobile apps). They are all using the same database. Right now each one has its own website. But each website cost money. So how can I use just one website to have them altogether? Something like this:
www.myapp.com - for the web application
www.myapp.com/admin -for site admin
www.myapp.com/webapi - for web api
If we have our own IIS, I know we can use virtual directory. But with Azure, how can I achieve this?
I think this article explained it
Create three projects (web, admin, and api)
Assign admin and api to their appropriate virtual directory
Publish the root project (web)
Set up virtual directory in azure portal
Publish the child projects
I want to know if there are any projects that use DNN 7 to interact with SharePoint 2013. The SharePoint 2013 is a Provider hosted. For the setup, DNN would be installed on the same server as the App server and SharePoint 2013 on a separate server. Normally, I would create a SharePoint app that would be installed on the App server. I want to do the same using DNN as the framework with the module as the SharePoint App. Is this possible? I would assume so since SP2013 uses client model. Should I create the SharePoint App project and included it in my DNN project?
Thanks in advance.
You can embed SharePoint apps in DotNetNuke by making use of a html module that embeds your app in an iframe element. But since your apps can be hosted on any web hosting stack, you can even probably create a DotNetNuke module that is a Sharepoint app.
You will have to register your app with Azure ACS and with the App Management Service of the SharePoint farm or SharePoint Online tenancy, to be able to establish communication.
Then, to access Sharepoint, you will have to pass an access token in each HTTP request that you can obtain from Microsoft Azure Access Control Service.
More info here.
Current App and website environment;
ASP.NET app written in C# hosted on a Windows web server and linked to from a site hosted on a SharePoint 2010 server.
Purpose of App;
Download link calls a downloader that generates a custom signed build of the app and logs the download to a SharePoint list.
Site has been redesigned and migrating to SharePoint 2013, looking at a provider-hosted solution for the ASP.NET app and I was wondering if it is possible to generate a build with/on an Azure solution.
Thanks!
Yes is possible.
The only thing which you have remember is add in your App a clientWebPart. And configure it with url to your asp.net site.
Because when you add your app in page, you must go add how Client App Part or WebPart.
I have a mvc web application hosted on iis and SharePoint installed on another machine. The Web application read the directory on SharePoint. How can I authenticate all the request coming from the machine on which mvc web application is deployed on SharePoint? or how can I impersonate all request to a service account which has permission to access the SharePoint?
Please provide a link with some information how can I achieve this as I am new to SP 2013