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

MIM portal best practices


The following are some best practices of the MIM portal:

  • Minimize the use of dynamic nesting and the use of negative (NOT) conditions in sets and groups. A good rule of thumb is to stay under five NOTs.

  • Disable the verbose tracing of MIM Service when not needed.

  • Be aware that exposing self-service reset internal and external could be a Denial of Service endpoint if you have Active Directory configured to lock out.

  • Back up custom workflow code and pages and manage them as you would any production source code.

  • Do not delete the default workflows that come with the product.

  • Keep an eye on expired portal requests. If you see requests building up beyond the retention time (default 30 days), then you may need to run the SQL job FIM_DeleteExpiredSystemObjectsJob.