We have now been creating SharePoint-hosted apps for SP on-line with nice success, however looks like creating SharePoint-hosted apps for the on-premise 2013 isn’t so intuitive course of.
- As a rule of thumb, ought to we NOT create sharepoint-hosted apps on the on-premise?
For each new deployment model, until customers go to Web site Content material and Belief the app, it wont seem on the with X-Body-Possibility = SAME ORIGIN error. Word that each one of my ClientWebParts embrace the AllowFraming tag. We additionally use loads of the AppContextSite Lists.
Is not there any approach to set my app as trusted, in order that any person visiting the web page internet hosting the AppPart, have the ability to see the content material of my app?
- None of this points exist on the web model and i used to be questioning if the sharepoint-hosted apps will not be meant to be deployed on the on-premise.
** This thread relies on one other thread i raised not too long ago, however I believed to create a brand new one for narrowing the issues I’ve! Don’t down-vote for duplication !
UPDATE 1: level 2 revised
In level 2 I discussed that my app requires Belief from all customers. The proper is that the app requires login from all customers visiting Web site Contents earlier than they’ll view it on the web page. Right here is the revised level 2.
- For each new deployment model, until customers go to Web site Content material open the app and insert their credentials, it wont seem on the web page with X-Body-Possibility = SAMEORIGIN error. Word that each one of my ClientWebParts embrace the AllowFraming tag. We additionally use loads of the AppContextSite Lists.
Is not there any approach to login with out going to the Web site Contents or occasion higher to make use of the Web site credentials and login immediately with out further effort from the person?