Book Image

Microsoft Identity Manager 2016 Handbook

By : David Steadman, Jeff Ingalls
Book Image

Microsoft Identity Manager 2016 Handbook

By: David Steadman, Jeff Ingalls

Overview of this book

Microsoft Identity Manager 2016 is Microsoft’s solution to identity management. When fully installed, the product utilizes SQL, SharePoint, IIS, web services, the .NET Framework, and SCSM to name a few, allowing it to be customized to meet nearly every business requirement. The book is divided into 15 chapters and begins with an overview of the product, what it does, and what it does not do. To better understand the concepts in MIM, we introduce a fictitious company and their problems and goals, then build an identity solutions to fit those goals. Over the course of this book, we cover topics such as MIM installation and configuration, user and group management options, self-service solutions, role-based access control, reducing security threats, and finally operational troubleshooting and best practices. By the end of this book, you will have gained the necessary skills to deploy, manage and operate Microsoft Identity Manager 2016 to meet your business requirements and solve real-world customer problems.
Table of Contents (22 chapters)
Microsoft Identity Manager 2016 Handbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Temporal sets


In many situations when we manage users, we are working with time-dependent actions.

For example, we might state that a user should be disabled in Active Directory the day his/her employment ends, but should be deleted from AD 30 days after the end of their employment. How do we do that in MIM?

First of all, we need to get the employment dates into MIM. Usually, we get them from the HR system. It is a bit tricky to work with date/time attributes, since localization and formatting can require us to do some troubleshooting before we get it right. You will very likely end up using the built-in DateTimeFormat function when importing date/time data from HR or some other source, and converting it to the yyyy-MM-ddTHH:mm:ss.000 format used in MIM.

We then create what is called a temporal set. This is just a normal set, but we use a criterion that is time-dependent:

We can then use this set to trigger an MPR that modifies an attribute, such as the active attribute I used in my previous...