archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Provider-hosted apps on premises, part 3 - Blog - Mavention
    s start page make sure the website is started and available Most likely the error is caused by either a stopped website or a misconfiguration in your dns An error has occurred while processing your request This error indicates something has gone wrong while setting up or performing authentication for the app When a developer creates an app using visual studio a c class is generated named TokenHelper The code in this class handles the token based authentication used for authentication between SharePoint and the app Unfortunately the TokenHelper does not perform any logging unless the developer has added it to the generated code which is not likely since most developers including myself will refrain from modifying generated code With this is mind we can start looking for the actual problem ClientId First of all check if the web config of the appweb contains the correct ClientId of the app You ve already used this guid when registering the app on your site and you can parse the ClientId from your app file if necessary Make sure the ClientId is correct including the casing of the guid Anonymous access Another common cause for this error is allowing anonymous access to the app web With anonymous access allowed the web server will not force an authentication challenge resulting in this error message Check if anonymous access is allowed on the site You can double check by manually typing the address of your appweb start page in the address bar of your browser If you re copying the url from the address and pasting it into a new window make sure you remove the querystring to avoid being redirected by the app An example start page address is https myapp mavention apps nl pages default aspx Token issuer The trusted security token issuer is another common cause for this error First of all make sure the IssuerId guid in the web config matches the guid in the RegisteredIssuerName property of the trusted token issuer You can retrieve this value using PowerShell Get SPTrustedSecurityTokenIssuer select Name RegisteredIssuerName Format List The IssuerId guid should match the first part of the RegisteredIssuerName It is possible to have more than one token issuer The name should help you determine which token issuer to specify in the web config Every trusted token issuer should have a valid RegisteredIssuerName If you see an empty guid in the list 00000000 0000 0000 0000 000000000000 this is likely the cause of the problem since this makes the token issuer invalid An invalid token issuer will cause problems even if it s not the token issuer you are using for your app If you see an empty guid make sure you remove the invalid token issuer using the Remove SPTrustedSecurityTokenIssuer command in PowerShell Certificate errors The app needs access to a certificate in order to encrypt and decrypt the tokens exchanged with the token issuer The location of the certificate and its password is stored in the web config First of

    Original URL path: http://www.mavention.nl/blog/provider-hosted-apps-premises-part-3 (2016-02-18)
    Open archived version from archive


  • Frans van Rijn - Mensen - Mavention
    maken van technische taal naar een voor iedereen te begrijpen taal Met zijn gedrevenheid en passie voor SharePoint wil hij het maximale uit het platform halen Zijn hamvraag bij projecten is Waarom doen we het Zijn grootste drijfveer is namelijk om SharePoint nuttig in te zetten voor organisaties De technische oplossing moet iets toevoegen aan de dagelijkse praktijk SharePoint WCM Specialist Mavention is specialist op het gebied van public facing

    Original URL path: http://www.mavention.nl/mavention/mensen/frans-van-rijn (2016-02-18)
    Open archived version from archive

  • Provider-hosted apps on premises, part 2 - Blog - Mavention
    s Register the app in your site collection s Next we ll need to register the app in the site collections you ll want to use it in This step will need to be repeated for every site collection that will use the app Open the following url in your browser SiteCollectionUrl layouts 15 appregnew aspx On my development environment this would be https demo mavention local layouts 15 appregnew aspx and fill out the form on the page ClientSecret is a required field but since it s only used for low trust apps we can just generate a random key and leave it at that The same goes for app domain and app redirect uri These fields are not used in this scenario so you can just use dummy values for these fields Your supplier or developer should have provided you with the ClientId In case they didn t or you just aren t sure if it the ClientId is correct there is a simple trick to learn your app s ClientId We can extract the ClientId from the app file by renaming the app file to a zip file and opening it in windows explorer The file you re looking for is called AppManifest xml Simply open this file in notepad or whatever text editor you re comfortable with and note the ClientId The appregnew form creates an app principal It can also be set up using PowerShell I ve chosen the web approach since most people are familiar with this screen already and it s also supported in an online scenario Add the app to your site s Open the site contents page on the site where you want to use the app and click on Add an app The app you ve just added should be one of the first apps in the list Alternatively you can use the search box to find it Click on the app to install it The popup will inform you of the permissions the app will have on your farm Click Trust it to install the app If the permissions do not match what you expected click Cancel and contact your developer or supplier If you want to use the app in subsequent sites this step will need to be repeated for all of them We now have the SharePoint part of the app installed Let s move on to installing the AppWeb Install the AppWeb on your app server The idea behind provider hosted apps is making sure managed code does not run on SharePoint Therefore I do not recommend hosting the managed code of your provider hosted app the AppWeb on a SharePoint server This might be ok for a development environment but in a production scenario I would recommend introducing an app server for this purpose On your app server go to your web server instance most likely IIS but note that provider hosted apps are not limited to the Microsoft stack when it comes to the

    Original URL path: http://www.mavention.nl/blog/provider-hosted-apps-premises-part-2 (2016-02-18)
    Open archived version from archive

  • Provider-hosted apps on premises, part 1 - Blog - Mavention
    provider hosted app brings two very powerful tools to the table managed code and high trust With managed code the developer is free to use any programming language he or she deems fit for the task However the app model does not allow managed code to be installed directly on SharePoint This seems like a deficit at first but it is easily resolved by introducing an app server and hosting the code there All we need is a separate website for example on IIS On my development environment I suffice by simply adding a separate IIS site on the SharePoint server This keeps the app code separate from SharePoint without introducing new infrastructure Obviously this is not advised for a production scenario High trust apps can have their own set of permissions and are as opposed to low trust apps not constrained by the permissions of the user This means that a high trust app can perform actions for a user which the user him of herself is not allowed to perform A tightly controlled form of elevation In summary if you require server side managed code or if you need some sort of context elevation a provider hosted could the correct choice How does it work A provider hosted app consists of two parts the app for SharePoint and a website that contains the actual code called the AppWeb Since the AppWeb is not actually part of SharePoint but runs on a separate site or server the high trust on premises scenario requires that we re able to create a trusted connection between SharePoint and the AppWeb On SharePoint 2013 authentication and trusts are managed by passing tokens to one another thereby confirming identity This is also the main reason why SharePoint 2013 farm should always be hosted on

    Original URL path: http://www.mavention.nl/blog/provider-hosted-apps-on-premises-part-1 (2016-02-18)
    Open archived version from archive

  • Inconvenient list content type inheritance using CSOM - Blog - Mavention
    spContext CreateUserClientContextForSPHost load web and list clientContext Load clientContext Web clientContext ExecuteQuery var list clientContext Web GetList sites dev en SitePages clientContext Load list clientContext ExecuteQuery content type id of Image var parentContentTypeId 0x0101009148F5A04DDD49CBA7127AADA5FB792B00AADE34325A8B49CDA8BB4DB53328F214 EnsureContentTypeFields clientContext list parentContentTypeId var info new ContentTypeCreationInformation set up new content type inheriting from Image Id parentContentTypeId 00 9F13E4D76C8843D6BAF5EACD8EE880AB Name MyNewContentType add new content type to the list list ContentTypes Add info clientContext ExecuteQuery The result is as follows Note that the fields from parent content type Image are missing in the new content type Debugging this on my local farm I discovered that the fields are actually added to the list content type as expected The problem is not that the content type is inherited incorrectly but that fields are not pushed to the list Since the fields are not present in the list SharePoint hides them in the content type as well The solution is to manually push the fields to the list prior to provisioning the content type protected void Page Load object sender EventArgs e The following code gets the client context and Title property by using TokenHelper To access other properties the app may need to request permissions on the host web var spContext SharePointContextProvider Current GetSharePointContext Context using var clientContext spContext CreateUserClientContextForSPHost load web and list clientContext Load clientContext Web clientContext ExecuteQuery var list clientContext Web GetList sites dev en SitePages clientContext Load list clientContext ExecuteQuery content type id of Image var parentContentTypeId 0x0101009148F5A04DDD49CBA7127AADA5FB792B00AADE34325A8B49CDA8BB4DB53328F214 EnsureContentTypeFields clientContext list parentContentTypeId var info new ContentTypeCreationInformation set up new content type inheriting from Image Id parentContentTypeId 00 9F13E4D76C8843D6BAF5EACD8EE880AB Name MyNewContentType add new content type to the list list ContentTypes Add info clientContext ExecuteQuery protected void EnsureContentTypeFields ClientContext context List list string contentTypeId get the content type context Load list ParentWeb AvailableContentTypes context ExecuteQuery

    Original URL path: http://www.mavention.nl/blog/inconvenient-list-content-type-inheritance-csom (2016-02-18)
    Open archived version from archive

  • Mavention Document Miner app for Windows Phone available in the store now - Blog - Mavention
    app for Windows Phone which provides us with exactly that In addition it provided a great opportunity to get our hands dirty working with the Office Graph API The Mavention Document Miner provides a simple and easy to use interface to quickly access the information you require from your Office365 environment The pivot based interface navigates through the different views quickly You ll recognize most of the views from the Delve web interface but we ve started adding a few more to make getting to what you need even easier Currently the Mavention Document Miner supports a free text search trending around me home my work and shared items views you know from Delve and views to get the document you ve recently viewed and documents which are trending in sites you follow We ll continue to add more view in upcoming releases Version 1 3 is available in the Windows Phone Store now You ll need Windows Phone version 8 1 in order to install it on your device Please feel free to let me know what you think of the app and any features you would like to see in a future release Building SharePoint apps with SignalR

    Original URL path: http://www.mavention.nl/blog/mavention-document-miner-app-windows-phone-store (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    21 8 2014 door Frans van Rijn Building the Isala folders Windows Store app Together with Isala Mavention developed a Windows Store app centered on these brochures to easily disclose the information available here to a broader audience This blog discusses a few of the technical challenges we encountered during this development Aangemaakt op 27 5 2014 door Frans van Rijn Building SharePoint apps with SignalR Inspired by a recent

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Frans+van+Rijn%22&start=6 (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    items Frans van Rijn 12 Duet Enterprise features available on SharePoint Online Duet Enterprise features available on SharePoint Online Aangemaakt op 7 5 2014 door Frans van Rijn Confusing content type name updates using powershell In this blog post we ll discuss renaming content types using PowerShell on SharePoint 2013 Aangemaakt op 28 4 2014 door Frans van Rijn 1 2 3 Functionele SharePoint consultant Als functionele SharePoint Consultant realiseer

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Frans+van+Rijn%22&start=11 (2016-02-18)
    Open archived version from archive



  •