Hotfix rollup package (build 4.4.1459.0) available for Microsoft Identity Manager 2016 SP1

Yesterday Microsoft released a new hotfix rollup package for Microsoft Identity Manager 2016 SP1.

This hotfix contains a lot of improvements and in addtion fixes several issues which cannot all be listed here.
One major improvement is the support of:

SQL 2016 Always On Availability Groups

and

System Center Service Manager 2016 Reporting supportability

See more details on the following blog posts and KB article:

Hotfix rollup package (build 4.4.1459.0) is available for Microsoft Identity Manager 2016 Service Pack 1

Download Update for Microsoft Identity Manager 2016 SP1 (KB4012498)

Supported platforms for MIM 2016

Identity and Access Management Support Team Blog

New versions of additonal FIM/MIM connectors released

New version of the additional FIM/MIM connectors are relased some days ago.

This connector package contains the following connectors:

There are a couple of fixes and enhancements on those connectors, you can get the complete list from the version release history:

https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnectsync-connector-version-history

(And yes, the placement of the documentation also makes no sense to me since these are FIM/MIM only connectors)

Connectors can be downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=51495

 

MIM Portal: regular user access and unable to process your request

Getting the error „Unable to process your request“, is a common issue a lot of people are facing when accessing the FIM/MIM portal a regular user.

There are a lot of forums discussions and blog posts around that issue and how to solve it.

However, I think I found another reason why that issue can occur even if that will not be a common scenario for most people but still worth to write about it in my opinion.

Read more of this post

Lithnet FIM/MIM Synchronization Service PowerShell Module released

Ryan Newington (Developer of FIM/MIM Lithnet PS Module, new FIM/MIM Service Client and RestAPI) already anounced new PowerShell Cmdlets for the FIM/MIM Synchronization Service on the last MIM Team User Group Meeting.

You can now download that module on github.

See documentation on the modules and also the disclaimer.

Download the FIM/MIM Sync PowerShell Module.

Great job again Ryan.

Here is a list of modules included:

Read more of this post

MIMTeam User Group: MIM Handbook and upcomming MIM features

At the last MIM Team Usergroup meeting last week, David Steadman and Jeff Ingalls talked about their journey of writing the upcomming new MIM 2016 Handbook which is expected to be released in July.

Beside some very interesting facts on their experience and some funny things, there where one slide from David talking abount upcomming MIM 2016 CTP (preview) feature which fill then be comming to MIM GA some time in future.

Here is a screenshot of that slide:

MIMUpcommingCTPs

One of the most interesting facts I think is the support of Exchange Online for approvals, so you do not need to have your FIMService mailbox be onPremises, while you are maybe having already all other mailboxes migrated to O365.

Also all the feedback seems to be recognized by Microsoft so we can see their will be a PAM Single forest deployment scenario.

A lot of you I guess will also like the Cross Browser Support for MIM components lile SSPR and Portal.

So stay tuned for that and have a look to Microsoft Connect (Identity and AccessManagement Site) where those new CTPs will arrive.

 

Creating Mobile Apps for MIM with PowerApps and Lithnet RestAPI

I recently take a look into the Preview of Microsoft PowerApps and also Microsoft Flow. There are some really cool examples and templates for PowerApps and I also like that it is possible to create custom API connection for nearly every RestAPI.

When thinking on MIM we have that great Lithnet RestAPI from Ryan Newington and so a new project was born in my spare private time. Here are the results.

In order to create a connector in PowerApps for custom APIs we need a Swagger JSON definition file which describes the API (calls, parameters and so on). You can easily create such a definition file with the Swagger Editor in YAML. (Don’t worry, I’ve done this for you).

If you want to take a better look to the API definition file, go to http://editor.swagger.io and paste the YAML or JSON file of the Lithnet RestAPI into the editor. You will find both files at the end of the post.

These are the steps to setup the environment and create a simple PowerApp:

Install Lithnet Rest API:

First we assume you have a running MIM 2016 or FIM 2012 R2 installation. In that solution install the Lithnet FIM/MIM RestAPI according to the documentation: http://lithnetrmws.codeplex.com

Read more of this post

Authorize MIM Portal user image upload with Microsoft Cognitive Services

I saw these great videos from //build keynote some weeks ago about the Microsoft Cognitive Services and I was really impressed. I know these APIs like face, emotion, speech are designed for other purposes but I was thinking to myself on who to benefit from them for identity management.

So I remembered some time ago when talking about MIM Portal as a user self-service portal for personal data some customers find it is sometimes not a good idea if users can upload their own photos. The arguments where that photos cannot be validated in that way that it really belongs to that person. So people could upload for example funny pictures and avatars or even more bad images.

Sure, you can handle this by organizational policies, but I was thinking of a technical solution. At this point when thinking about Microsoft Cognitive Services the Face API came to my mind.

If you check the Face API it has methods for face detection in images and also face identification or verifying. You can also create person groups and persons with multiple faces saved in Azure if you want.

But for my little demo I only need the face detect and verify methods.

So here is how this demo works:

If people upload new images to MIM Portal, I trigger an authorization workflow and get the current and new photo with an MIMWAL update resource activity and pass that data to a PowerShell script which then calls the Face API.

The PowerShell Script uploads both images to Azure to do a face detection within the image and then returns a faceId for each of the pictures. Images are saved 24 hours Azure.
Read more of this post

%d bloggers like this: