Username or Email Address
Some people still consider PowerShell as something that you need to employ only for scripting and automation scenarios, but, when it comes to Microsoft Technology stack, PowerShell evolved into the preferable way of configuring and managing your systems irrespectively of availability of corresponding graphical user interface (GUI). In fact, PowerShell is your primary tool for day to day administration and even some one-off tasks are no longer an excluded use case for PowerShell.
Today, PowerShell is not only an easier way to do some one-off changes or configuration tasks, sometimes it is the only way you can do them. There are a lot of situations when there is no parity in what you can do in GUI and PowerShell, and if in the early days of PowerShell, you sometimes could have a problem of not being able to do something available in GUI with PowerShell, nowadays we have rather the opposite situation – GUI often miss some basic things which available to you only in PowerShell.
Sample rating item
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.