PowerShell CLI should support single sign on for Windows

Current Situation

• The PowerShell CLI can be used with authentication and authorization.
• However, a PowerShell credentials object (account, password) has to be created and has to be passed on to the respectve cmdlets of the JobScheduler Module, e.g. Use-JobSchedulerWebService -Credentials,

Desired Behavior

• For Windows environments the PowerShell CLI should support single sign on, i.e. the account that is running the PowerShell session is considered being authenticated and its credentials are forwarded to the REST Web Service.
• The behavior should be configured by using a new switch Use-JobSchedulerWebService -UseDefaultCredentials

Maintainer Notes

• Branch 1.x of JobScheduler makes use of the Shiro authentication layer.
• Shiro is considered deprecated due to a standstill in feature development and delayed resolution of vulnerabilities in Shiro.
• See JOC-1145 for the deprecation announcement and the replacement that becomes available starting from Release 2.x
• With JOC-952 being ready an alternative way for single sign on with any platforms will be available.