About seven years ago at a conference in Los Angeles I attended I remember a session where a consultant from Oxford Computer Group gave a presentation on integrating Quest Identity Manager (now Dell One Identity Manager) with the Forefront Identity Manager Portal. I’ve recently had a requirement to do something similar and Carol pointed me in the direction of her experiments with doing something similar based off inspiration from that same presentation/session.
Well it is now 2017 and FIM and SharePoint have all moved through a few versions and doing something similar has changed. So now that I’ve got it working I thought I’d share how I’ve done it, and also to solicit any improvements. I’ve done this with SharePoint 2013.
In this post I’ll detail;
- Publishing a Power BI Report
- Creating new Microsoft Identity Manager Navigation Bar Resources
- Embedding as an IFrame the published Power BI Report in the Microsoft Identity Manager Portal so that it appears like below
Obviously to follow this verbatim you are going to need to have a Power BI workspace and a Power BI Report. But you could embed any page you want to test it out.
You’ll also need;
Publish a Power BI Report
In Power BI select a Report you are looking to embed in the MIM Portal. I selected License Plans under Reports from my Power BI Worksapce.
From the File menu select Publish to Web.
Select Create embed code.
Copy the link to your report somewhere where you can retrieve it easily later. Don’t worry about the HTML line or the size.
Download and install with the defaults SharePoint Designer 2013 from the link above. I’m using the 64-bit version. I installed it on my Development MIM Portal Server. I’m using 2013 as my MIM Portal is using SharePoint 2013 Foundation (with SP1).
Once installed start SharePoint Designer and select Open Site.
Enter the URL for your MIM Portal and select Open.
Note: In order for SharePoint Designer to successfully load your MIM Portal Site, the URL you provide above must be in your SharePoint Alternate Access Mappings. If it isn’t you will probably get the error “The server could not complete your request. For more specific information, click the Details button.”
And in your Windows Application Event Log Event ID 3 – WebHost
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/42194754
Exception: System.ServiceModel.ServiceActivationException: The service '/_vti_bin/client.svc' cannot be activated due to an exception during compilation.
Select Microsoft Identity Management, then All Files. You should then see a list of all the files in the MIM Portal website.
Locate the aspx folder, right click on it and select New => Folder. Create a new folder under the aspx directory named ‘reports’.
Right click on your new Reports Folder and select New => ASPX. Create an aspx file named reports.aspx.
Repeat to create another aspx file named report.aspx.
Click on the Reports.aspx file form the main pane and put the following contents in it overwriting everything else. Select Save.
<%@ Page Language="C#" %>
<meta name="WebPartPageExpansion" content="full" />
Click on the report.aspx file and replace the contents with the following and select Save.
Replace <yourreportlink> in https://app.powerbi.com/view?r=<yourreportlink> with your Power BI link.
<%@ Page masterpagefile="~masterurl/custom.master" Title="Reports" language="C#" inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version=22.214.171.124, Culture=neutral, PublicKeyToken=71e9bce111e9429c" meta:progid="SharePoint.WebPartPage.Document" UICulture="auto" Culture="auto" meta:webpartpageexpansion="full" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=126.96.36.199, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=184.108.40.206, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<asp:Content ContentPlaceHolderID="PlaceHolderTitleBar" Visible="true" runat="server">
<asp:Content id="content1" ContentPlaceHolderID="PlaceHolderMain" runat="server">
MIM Portal Navigation Resources
Now we need to create the MIM Portal Navigation Resources to link to our new files.
In the MIM Portal Select Navigation Bar Resources. Select New.
Provide a Display Name, Description and select Next. Ignore Usage Keyword for now. More on that later.
Make the Parent Order 8 to have it at the bottom of the Left Nav bar. Order is 0 as this is going to be our Group header. Select Next.
Provide the path to the Reports.aspx file ~/IdentityManagement/aspx/reports/reports.aspx Select Next.
Provide the Localised Display name, select Finish and then Submit.
Repeat, this time for linking to ~/IdentityManagement/aspx/reports/report.aspx and name it Licensing Report or whatever makes sense for your report. Also make the Order 1 so it nests under Reports.
Perform an IISReset.
Refresh you MIM Portal Page and you should see your new menu items on the left Navigatin Bar at the bottom.
Click on Reports and your Licensing Report will auto-magically load. Same as if you click on Licensing Report. You can now add as many reports as you need. And change which report you want to be the default by updating the Reports.aspx file in SharePoint Designer.
You will probably also want to limit who see’s what reports. You can do that through Usage Keywords and Sets etc. By default as described here the reports will only be visible to Administrators. Details to get you started on changing who can see what can be found here.
Let me know if you have any improvements.
Follow Darren Robinson on Twitter