laleh https://docs.microsoft.com/archive/blogs/laleh/feed.xml Wed, 17 Apr 2019 04:09:26 GMT en-US hourly 1 Call secure azure hosted API from SharePoint online https://docs.microsoft.com/archive/blogs/laleh/85 Tue, 20 Dec 2016 13:04:41 GMT https://blogs.msdn.microsoft.com/laleh/?p=85 Configuration Azure API 
  1. Create azure API , You can read aboutAzure API apps here and follow a good Getting started tutorial here. 
  2. Publish your azure API in azure, check the API
  3. Browse to azure portal, select your API application , select Authentication/Authorizations
  • Set the App Service Authentication: On
  • Action to take when request us not authenticated: Log in with Azure dictionary
  • Authentication providers: Express
1  
  1. Now the API is protected with Azure AD, if you navigate your API via browser you will be prompted for login
  2. When we set authentication in Express mode, the app will be created automatically in Azure Active directory, you can see the name under Azure AD app
  3. Brows to Azure management portal, click on active directory in left navigation2
  4. Click on the Directory which will be federated to your office 365 (or any source you want to call azure API which uses the same azure active directory as your configured for you API authentication)
  5. Click on the Application, and you will find you AD app in the list which has been created with Express method as we discussed om step nr.3
  6. Now we need to create new app in AAD which will be our communication channel from office 365 to Azure API, Click on ADD on footer
  7. Enter name and select “WEB APPLICATION AND/OR WEB AP” option
  8. For Sign in URL enter your SharePoint online Url which you are planning to call Azure API from
  9. For APP ID URL, enter unique Url, this will be used as a unique logical identifier for your app.
  10. After the app created, click on Configure, copy the Client ID which will be used later­­
  11. Under Permission to other applications, Click “Add Application”, on the next page select “All Apps” and select you Azure API app which you double checked in step nr.8, and confirm
  12. You will be redirected back to Configure page, Under Permission to other applications, now you see your azure API app is listed here, click on delegated permission, select the access to app
  13. At the bottom of the page, click Manage manifest > Download manifest.
  14. Download the file to a location where you can edit it.
  15. In the downloaded manifest file, search for the oauth2AllowImplicitFlow Change the value of this property from falseto true, and then save the file.
  16. Click Manage manifest > Upload manifest, and upload the file that you updated in the preceding step.
  17. Azure management portal, select setting and copy your AAD subscription ID for related AAD
3 Call Azure API from SharePoint Online Once the above steps have been done, you can call azure API from sharePoint online  which is using same Active directory above
  1. Edit the page and add Script Editor web part
  2. Add following script
    • subscriptionId, see step nr.20
    • clientId see step nr.13
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js"></script> <script src="https://secure.aadcdn.microsoftonline-p.com/lib/1.0.13/js/adal.min.js"></script> <script type="text/javascript"> function CallAzureAPI() { "use strict"; var subscriptionId = "xxxxxxxxxxxxxxxxxxxxxxxxxx"; var clientId = "xxxxxxxxxxxxxxx";   window.config = { subscriptionId: subscriptionId, clientId: clientId, postLogoutRedirectUri: window.location.origin, endpoints: { AzureApiUri: 'https://xxxxxx.azurewebsites.net' }, cacheLocation: 'localStorage' // enable this for IE, as sessionStorage does not work for localhost. }; var authContext = new AuthenticationContext(config); // Check For & Handle Redirect From AAD After Login var isCallback = authContext.isCallback(window.location.hash); authContext.handleWindowCallback(); if (isCallback && !authContext.getLoginError()) { window.location = authContext._getItem(authContext.CONSTANTS.STORAGE.LOGIN_REQUEST); } // If not logged in force login var user = authContext.getCachedUser(); if (user) { // Logged in already console.log(user); } else { // NOTE: you may want to render the page for anonymous users and render // a login button which runs the login function upon click. authContext.login(); } // Acquire token for Files resource. authContext.acquireToken(config.endpoints. AzureApiUri, function (error, token) { // Handle ADAL Errors. if (error || !token) { console.log('ADAL error occurred: ' + error); return; } var ApiUri = "https://xxx.azurewebsites.net/api/GET"; $.ajax({ type: "GET", url: ApiUri, headers: { 'Authorization': 'Bearer ' + token, } }).done(function (response) { console.log('Successfully called API.'); console.log(response);   }).fail(function () { console.log('Calling API failed.');   }); }); } </script> <input type='button' value='Call Azure API' onclick=" CallAzureAPI ();"/>]]> Azure subscription in Azure Resource manager https://docs.microsoft.com/archive/blogs/laleh/azure-resource-manager Mon, 29 Aug 2016 20:02:51 GMT https://blogs.msdn.microsoft.com/laleh/?p=75 PS C:\> Get-AzureRmSubscription –SubscriptionName "your subscription" | Select-AzureRmSubscription normally remember most of classic model commands will follow with rm and end of the verbs. read more about it https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/]]> workflow failed with Unauthorized error https://docs.microsoft.com/archive/blogs/laleh/workflow-failed-with-unauthorized-error Tue, 13 Jan 2015 02:25:00 GMT https://blogs.msdn.microsoft.com/laleh/2015/01/13/workflow-failed-with-unauthorized-error/  when workflow failed ro start with this error :

Retrying last request. Next attempt scheduled in less than one minute. Details
of last request: HTTP Unauthorized to
https://sitename/_vti_bin/client.svc/web/lists/getbyid(guid'guid') Correlation
Id: id Instance Id: id

 uls :

01/12/2015 19:21:04.06 w3wp.exe (NLAMSPSHWF001:0x2B80) 0x2778 SharePoint Foundation Claims Authentication ae0tc High The registered mappered failed to resolve to one identity claim. Exception: System.Runtime.InteropServices.COMException (0x800703FA): Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA).     at Microsoft.SharePoint.Library.SPRequest..ctor()     at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous)     at Microsoft.SharePoint.SPRequestManager.GetContextRequest(SPRequestAuthenticationMode authenticationMode)     at Microsoft.SharePoint.Administration.SPFarm.get_RequestAny()     at Microsoft.SharePoint.SPSecurity.GetCurrentUserTokenNoApplicationPrincipalDelegated(SPWebApplication webApp, Uri siteUrl)     at Microsoft.SharePoint.SPSecurity.GetCurrentUserToken()     at Microsoft.SharePoint.SPSecurity.EnsureOriginatingUserToken()     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetMappedIdentityClaim(Uri context, IEnumerable`1 identityClaims)     at Microsoft.SharePoint.IdentityModel.SPIdentityClaimMapperOperations.GetClaimFromExternalMapper(Uri contextUri, List`1 claims) 324f82b4-5cee-fea5-86a9-368c6e129213

 solution:

 first make sure the STS ApplicationPool identity has full control on UPA.

  • In InetMgr, go to advanced settings for Security Token Service Application Pool
  • change "Load User Profile" to true.
  • Recycle application pool
]]> Get-spfarmconfig has misleading value https://docs.microsoft.com/archive/blogs/laleh/get-spfarmconfig-has-misleading-value Wed, 24 Sep 2014 06:31:00 GMT https://blogs.msdn.microsoft.com/laleh/2014/09/24/get-spfarmconfig-has-misleading-value/ You may notice if you run Get-spfarmconfig you will receive  following output  

 

you can change the value of WorkflowBatchSize via set-spfarmconfig

 And then if you try to run the equivalent command in stsadm (stsadm -o getproperty -pn workflow-eventdelivery-batchsize) you will notice there is no actual change in WorkflowBatchSize by "set-spfarmconfig"

This is a known issue and one of the properties returned by get-spfarmconfig in powershell is the WorkflowBatchSize property. However,The value of this property is not actually the workflow batch size, it is the work item batch size.Changing this property will change the work item batch size, and have no effect on the workflow batch size.

As workaround to change the workflow batch size,the stsadm command below has to be used:

stsadm.exe -o setproperty -propertyname workflow-eventdelivery-batchsize -propertyvalue <value>

 

]]> SharePoint 2013 workflow troublehsooting https://docs.microsoft.com/archive/blogs/laleh/sharepoint-2013-workflow-troublehsooting Wed, 03 Sep 2014 06:40:00 GMT https://blogs.msdn.microsoft.com/laleh/2014/09/03/sharepoint-2013-workflow-troublehsooting/ If you are using workflow manger in sharepoint 2013 you might face different issues  which you are not sure either the issue is comming form workflow manger or sharepoint , by following troubleshooting check list you might find at least the area you need to focus more

 

check list in workflow manager server  :
1. Check https://[wfms]:12290 or https://[wfms]:12291 if they are responding
2. Check ”WorkflowMgmtPool” is started
3. Following services are running

  • Workflow Manager Backend
  • Service Bus Message Broker
  • Service Bus Gateway
  • Windows Fabric Host Service (FabricHostSvc)


4. Get workflow farm information , workflow database  by  Start Workflow Manager PowerShell
• get-WFfarm
 
5. Check if the Workflow Manager farm running(workflow service backend and  front end should be rennin)  by  Start Workflow Manager PowerShell
• get-WFfarmStatus


 
6. Check oAut in accessible by https:// [wfms]:12291/$SYSTEM/$Metadata/json/1

7. Restart the WorkflowServiceBackend service

  • net stop WorkflowServiceBackend
  • net start WorkflowServiceBackend

 

If all is fine then time to focus on sharepoint :)

check list SharePoint server :

1. check if you are at least in version March PU 2013
2. Check “workflow service application” started
3. Check , workflow service application “workflow is connected”
4. Check “User Profile Service”
5. Check “App Management Service” is started
6. Check https://[FQDN]:12290 or https://[FQDN]:12291 if they are responding
7. Check https://[myserver]/Lists/Workflow History for error message
8. Check in SharePoint designer if you see workflow 2013 option


 

 

9. Try to register workflow manager
Register-SPWorkflowService –SPSite "https://myserver/mysitecollection" –WorkflowHostUri "https://workflow.example.com:12290"  –force


10. Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.
11. Make sure workflow initiator is not a system account
12. workflow initiator must have a user profile
13. Check following " Microsoft.SharePoint.WorkflowServices.Activities.dll" version are sync with each other

  •  C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SharePoint.WorkflowServices.Activities\v4.0_15.0.0.0__71e9bce111e9429c   Will be installed with Developer tools
  •  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\WorkflowActivities  Will be installed with SharePoint
  •  Database "WFResourceManagementDB", table "Scopes", path "SharePoint "check the default workflow configuration xml  file 


 14. We recommend to have all SharePoint and workflow manager (Office developer tools  in development environment ) sync and have in latest version

 

Hope it helps :)

]]>