Register-SPWorkflowService : The root of the certificate chain is not a trusted root authority
With my recent experience with workflow server configuration I encounter an error when tried to register workflow service with SharePoint 2013 farm. I want to connect workflow server to SharePoint web server where communication takes place via https. Earlier, when I configured the workflow farm, it automatically generates a SSL certificate for secure communication, but when I tried to run Register-SPWorkflowService command from SharePoint web frontend server it gives an error.
Command:
Register-SPWorkflowService -SPSite "https://SharePointSiteCollecitonURL" -WorkflowHostUri https://WorkflowServerFullName:12290/
Error:
Register-SPWorkflowService : The root of the certificate chain is not a trusted root authority.
At line:1 char:1
+ Register-SPWorkflowService -SPSite
"https://test/sites/W ...
+......+ CategoryInfo : InvalidData: (Microsoft.Share...WorkflowService:
RegisterSPWorkflowService) [Register-SPWorkflowService], ConfigurationExce
ption
+ FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell
.RegisterSPWorkflowService Issue:
The error message gave me a hint that the problem is related to the SSL certificate. The workflow server generates an automated SSL certificate for workflow web application on workflow server. When I tried to connect to workflow website from SharePoint front end server, it did not recognise the certificate.
Solution:
I have to copy the SSL certificate from workflow server to SharePoint front end server under the “Trusted root certification authority”.
Below are the steps to Export certificate from workflow server and import on SharePoint web server.
Go to command prompt and type “mmc” and hit enter
Go to file option from menu and select “Add/Remove snap-in”
Add “Certificates” to the right hand side and then click “OK”
Look for the workflow certificate which contains
Issue to: workflow server name
Issue authority: workflow server name
Export the certificate through wizard and then copy it to SharePoint web server
Import the certificate into SharePoint webserver via mmc under “Trusted root certification authority” location
Then navigate to https workflow site from SharePoint web server. You should be able to see the workflow site as appear below
Now run the below command to register workflow server where communication takes place via https
Register-SPWorkflowService -SPSite "https://SharePointSiteCollecitonURL" -WorkflowHostUri "https://WorkflowServerFullName:12290/"
It should run fine this time.
SharePoint 2013 Site Mailbox App Configuration
In SharePoint 2013 a site mailbox is a central email and document sharing account which a team can access from a SharePoint site. It will generate an email address; any mail sent to that email address will be accessible via mail box of SharePoint site depending on user permissions. For example a project team may decide to use a site mailbox to save all project related emails and important messages which are visible to all other team members.
Steps to Configure Mailbox app in SharePoint 2013 Team site
Navigate to “Site Contents” page
Click on “Add an App” link
Click of the “Site Mailbox” icon as appear below
Click “Add” button, the mail box app will be installed on your site and the below icon will appear in “Site contents” page with status as “Installed”.
You will also see “Mailbox” link inside “Quick launch” menu as appear below
Click on “Mailbox” link, this will start provisioning new mail box for your team site.
Once, the mailbox set-up is complete, the below screen will appear
Select Language and Time zone, then hit “Save”
It will open the “Outlook web app” with welcome email saying
“Now you can send mail to SMO-TestMailBox@eblogin.com and it will land in a mailbox just for the people in this site. Visit the mailbox on the Eblogin Team site to see for yourself”.
You can now CC emails at above address if you want to share them with other team members via mailbox.
To test this, I just sent an email to above address and it was showing inside new mailbox.
There are various ways to forward important email to your mail box which will help the team to collaborate in better way.
Failed to query the OAuth S2S metadata endpoint URI SP2013 register workflow service error
Couple of day ago, I setup new SharePoint 2013 UAT Farm for our new application testing. The application also contains several SharePoint 2013 workflows build in visual studio 2012.
For that reason I had to configure workflow server and connect it to SharePoint 2013 farm by using Register-SPWorkflowService command.
I tried to register Workflow Service in SharePoint 2013 Farm using below command.
Register-SPWorkflowService –SPSite "https://eblogin-Intranet.net/sites/WFConnection" –WorkflowHostUri "http://test-wfserver-01:12291/"
I received the following Error message in SharePoint management shell window.
PS C:\Users\ebloginadmin> Register-SPWorkflowService -SPSite " https://eblogin-Intranet.net/sites/WFConnection " -WorkflowHostUri "http://test-wfserver-01:12291/"
Register-SPWorkflowService : Failed to query the OAuth S2S metadata endpoint
at URI 'https://eblogin-Intranet.net/sites/WFConnection /_layouts/15/metadata/json/1'.
Error details: 'An error occurred while sending the request.'. HTTP headers
received from the server - ActivityId: 9d9e3fc8-39ac-40f9-b61b-93a117c04f60.
NodeId: test-wfserver-01. Scope: /SharePoint. Client ActivityId :
8a118525-866d-4539-9a69-ad747a7c1879.
At line:1 char:1
+ Register-SPWorkflowService -SPSite " https://eblogin-Intranet.net/sites/WFConnection”
-Workf ...
+...... + CategoryInfo : InvalidData: (Microsoft.Share...WorkflowService:
RegisterSPWorkflowService) [Register-SPWorkflowService], InvalidRequestExc
eption
+ FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell
.RegisterSPWorkflowService
PS C:\Users\ebloginadmin>As I did not have DNS published yet for my web application. So basically the Register-SPWorkflowService command was trying to connect to the SharePoint URL end point (http://xxxx/_layouts/15/metadata/json/1 ) which has the host header.
So to avoid this error I have added the SharePoint web application parent site collection URL to the Workflow manager server host file and was able to run Register-SPWorkflowService command
These are the steps to edit host file on workflow server
Right click on note pad on workflow server as select “Run as administrator”. Go to the file from menu option click “Open”
Navigation to the following location to open host file C:\Windows\System32\Drivers\etc
Select file type as “All Files” then then open the file called “Hosts”
Add new entry in the host file as
172.160.2.77 WorkflowSiteCollectionURLWitoutHttp
Note: 172.160.2.77 refer to the IP of your front end server hosting workflow web application and site collection, in my case the URL was (eblogin-Intranet.net)
Re-run the Register-SPWorkflowService command and you should be able to connect your workflow server with SharePoint farm.
Register-SPWorkflowService –SPSite "https://Your workflowsitecollecitonURL" –WorkflowHostUri "http://Workflow serverUrl:12291/"
Customise list field rendering in SharePoint 2013 using JS Link
Today I am going to show you that how easy it is to render SharePoint 2013 list fields the way you want via JSLink. For the purpose of this demo I have created a task list and updated the choice of “Priority” field to (Critical, High, Medium, Low) as appear below.
Now I want to show different background colours for different priority value to visualize the tasks in better way.
To do this, create a new file called RenderField.js and copy paste the below code.
// Create a namespace for our custom functions
var ebloginSpace = ebloginSpace || {};
// Create function for rendering the field value
ebloginSpace.myFiledRender = function ()
{
var myFieldOverride = {};
myFieldOverride.Templates = {};
myFieldOverride.Templates.Fields =
{
'Priority': { 'View': ebloginSpace.GetFieldColour }
};
// We need to register the rendering template
SPClientTemplates.TemplateManager.RegisterTemplateOverrides(myFieldOverride);
};
// Create a function to change the Priority Field background color depending on the selected value.
ebloginSpace.GetFieldColour= function (ctx) {
var Priority = ctx.CurrentItem.Priority;
if (Priority.indexOf("Critical") != -1) {
return "<div style='background-color: #F54949; display: block; padding-left: 10px; width: 100%;'>" + Priority + "</div>";
}
if (Priority.indexOf("High") != -1) {
return "<div style='background-color: #E890C2; display: block; padding-left: 10px; width: 100%;'>" + Priority + "</div>";
}
if (Priority.indexOf("Medium") != -1) {
return "<div style=';background-color: #DCF551; display: block; padding-left: 10px; width: 100%;'>" + Priority + "</div>";
}
if (Priority.indexOf("Low") != -1) {
return "<div style='background-color: #85DEA0; display: block; padding-left: 10px; width: 100%;'>" + Priority + "</div>";
}
return ctx.CurrentItem.Priority;
};
// Call the function.
ebloginSpace.myFiledRender();There are many ways to bind JS file to a list. You can bind it to content type , views, site columns, add reference in list view web part properties etc.
Upload the RenderField.js file to Styles library as shown below.
This is how task list look like before using our custom rendering JSLink file.
For this demo I have added JSLink to web part property of Task list view, under Miscellaneous section there is JS Link property, add RenderField.js file reference here. (Hint: ~sitecollection/styles/…..)
Apply the settings and stop editing the page form ribbon. The task list view “Priority” column data will render with different background colours depending on Priority value.
This is a simple example to show how easy it is to render list view fields the way you like.