Windows PowerShell Blog

On second thought I used something slightly different:

echo 'Enter the password to log in: '

$password = read-host -assecurestring

$credentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $user, $password

One advantage here is that it's a little less disruptive to the environment (no registry change).

Interesting. Some time ago, I created a function Get-ConsoleCredential for just this purpose. It is useful for creating a "su" analog among other things. Here's the relevant bit from my profile.

#starts a new powershell console with specified credentials, similar to su(1) on UNIX

function Substitute-User( [String] $username="root" )

{

if( $username -eq $null )

{

#look up the built-in Administrator account using WMI.

#the built-in administrator has a SID that starts with S-1-5 and ends with -500.

$accts = get-wmiobject win32_useraccount

foreach( $acct in $accts )

{

if( $acct.SID -match '^S-1-5-.+-500$' )

{

$username = $acct.Caption

break

}

}

}

$credential = Get-ConsoleCredential( $username )

$startinfo = new-object Diagnostics.ProcessStartInfo

$startinfo.UseShellExecute = $false

$startinfo.FileName = "$pshome\powershell.exe"

$startinfo.UserName = $credential.UserName

$startinfo.Password = $credential.Password

$startinfo.WorkingDirectory = $pwd

trap [ComponentModel.Win32Exception]

{

if( $_.Exception.NativeErrorCode -eq 267 )

{

write-host "$pwd is an invalid directory for $username."

write-host "Starting PowerShell in ${env:SystemRoot}\system32."

$startinfo.WorkingDirectory = "${env:SystemRoot}\system32"

$null = [Diagnostics.Process]::Start( $startinfo )

}

else

{

$_.Exception.Message

}

continue

}

$null = [Diagnostics.Process]::Start( $startinfo )

}

#Generate a PSCredential object without creating a pop-up security dialog like

#the built-in get-credential cmdlet.

function Get-ConsoleCredential( [String] $username=$( read-host 'Username' ) )

{

while( !($username) )

{

$username = read-host 'Username'

}

$passwd = read-host -asSecureString 'Password'

new-object Management.Automation.PSCredential $username, $passwd

}

# alias functions

new-alias cred Get-ConsoleCredential

new-alias su Substitute-User

why don't no add a parameter to get-credential in V2 so you can do this without a registry hack. Additional i presume this is the default behaviour in PS remoting?

By the way, this DOES NOT seem to work in Graphical Windows PowerShell V2 (CTP2). It always brings up the GUI dialog.

Jim

Forgot about posting the question here about getting a Notes ID.  After some trial and error I eventually had figured this out.  The following example will successfully allow the passing of a notes credential to the various Transporter Suite cmdlets without being prompted for the notes credentials:

To get and store the credential for the current user:

$notespw = Read-Host "Enter the password for the Notes ID file" -AsSecureString

$notespw | ConvertFrom-SecureString | Set-Content $pwfile -force

To retrieve the password and create the PSCredential object:

$notespw = get-content $pwfile | ConvertTo-SecureString

$notesid = new-object -typename system.management.automation.pscredential -argumentlist "-default-",$notespw

Example of use:

Get-DominoMailbox mary@contoso.com -SourceCredential $notesid