Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Credentials are objects that include the specification of a user account and password that can be used for authenticattion:
    • HTTP Authentication with a JobScheduler Master.
    • HTTP Authentication with a Proxy.
  • Credentials objects can be created once and can be re-used:
    • Credentials can be created within a PowerShell session. The PowerShell built-in Get-Credential cmdlet can be used to specify credentials on the fly, e.g. prompting the user for input of the user account and password.
    • Credentials can be created outside of a PowerShell session and can be used in a PowerShell session. The Get-JobSchedulerSystemCredentials cmdlet can be used to retrieve an existing credentials object for authentification with the JobScheduler Master.

...

Using the target name login_as_ap from the above example allows the user who owns this credential to retrieve the credentials object.

  • The Get-JobSchedulerSystemCredentials cmdlet accepts the target name of a system credentials object that is owned by the current user. This cmdlet returns a system credentials object.
  • The Set-JobSchedulerCredentials cmdlet expects a PowerShell credentials object, that is used for authentication when accessing the JobScheduler Master.
  • A conversion of system and PowerShell objects is required that can be achieved e.g. like this:

...

Explicit credentials can be specified with the Set-JobSchedulerCredentials cmdlet like this:

Code Block
languagepowershell
Set-JobSchedulerCredentials -Credentials $credentials

...

Explicit credentials can be specified on-the-fly with the Set-JobSchedulerCredentials cmdlet like this:

Code Block
languagepowershell
Set-JobSchedulerCredentials -AskForCredentials

...

Explicit credentials can be specified on-the-fly with the UseConnect-JobSchedulerWebServiceJobScheduler cmdlet -Url parametewr like this:

Code Block
languagepowershell
UseConnect-JobSchedulerWebServiceJobScheduler -Url http://root:root@localhost:4446 -Id scheduler111scheduler113

Explanations

  • The user account and password separated by a colon are preceeding preceding the hostname and are separated by a @ character from the hostname. 
  • Specifying credentials like this is considered insecure. 

...