Username or Email Address
In this blog post, I decided to put this AAD instance to more serious/interesting use and configure K2 SmartForms for AAD authentication. When configured, such AAD integration allows AAD users to log in to K2 SmartForms web sites (Runtime, Designer, Management) and enables K2 to use AAD users as destination users in workflows’ client events or pull users details via Azure Active Directory Service broker and respective SmartObjects.
In previous articles, we have installed Password Export Server Service (PES) 3.1, established trust, delegated permissions to source user account in the target domain, configured source and target domains for SID history migration and understood the theory behind interforest migration. Now, we move ahead with actual migration.
In the previous article, we have installed Password Export Server Service (PES) v3.1 on source domain and establish trust between two forests. We will move ahead and delegate permissions to user account from source domain in the target domain, configure source and target domains for SID history migration. We will also see the difference in behavior of AD objects in both intraforest and interforest migration and how to create an include file when migration large number of objects.
This new service gives you the possibility to have a domain controller on Azure, managed by Microsoft team. You’ll be able to join computers to the domain.
Interforest migration involves relocating Active Directory (AD) objects between forests.You may have to migrate AD objects between forests at the time of moving test domain into your production environment or because of companies merger and the need to consolidate two (information technology) IT infrastructures.