"cf login " interactive password prompt fails on cygwin

[gberche-orange]

password should be interactively prompted for when -p is omitted, regardless of whether -u was specified.

At least, it should be more user-friendly to remind users that if they prefer interactive login (to avoid having password recorded in their shell history) then they should omit both password and login, otherwise the password won't be prompted and auth will fail:

$ cf login -a https://api.run.pivotal.io -u user@domain.com -o myorg
API endpoint: https://api.run.pivotal.io
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
FAILED
Unable to authenticate.

API endpoint: https://api.run.pivotal.io (API version: 2.4.0)
Not logged in. Use 'cf.exe login' to log in.

$ cf --version
C:\Program Files (x86)\CloudFoundry\cf.exe version 6.1.2-6a013ca

[tjarratt]

Hey Guillaume,

What you're describing sounds like a real bug I saw a few weeks ago on windows. Could you provide a little more information? Are you using cmd.exe, powershell or Cygwin?

Sent From A Very Small Keyboard

On May 15, 2014, at 8:03, Guillaume Berche notifications@github.com wrote:

password should be interactively prompted for when -p is omitted, regardless of whether -u was specified.

At least, it should be more user-friendly to remind users that if they prefer interactive login (to avoid having password recorded in their shell history) then they should omit both password and login, otherwise the password won't be prompted and auth will fail:

$ cf login -a https://api.run.pivotal.io -u user@domain.com -o myorg
API endpoint: https://api.run.pivotal.io
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
FAILED
Unable to authenticate.

API endpoint: https://api.run.pivotal.io (API version: 2.4.0)
Not logged in. Use 'cf.exe login' to log in.

$ cf --version
C:\Program Files (x86)\CloudFoundry\cf.exe version 6.1.2-6a013ca
—
Reply to this email directly or view it on GitHub.

[gberche-orange]

You're right, it works properly with cmd.exe but fails within cygwin even if -u is not specified

$ cf login -a https://api.run.pivotal.io -o myorg
API endpoint: https://api.run.pivotal.io

Email> user@domain.com 
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
FAILED
Unable to authenticate.

API endpoint: https://api.run.pivotal.io (API version: 2.4.0)
Not logged in. Use 'cf.exe login' to log in.

I'm using cygin on win7

$ cygcheck.exe -V
cygcheck (cygwin) 1.7.27
System Checker for Cygwin
Copyright (C) 1998 - 2013 Red Hat, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I can send you privately the output of $ cygcheck.exe -s with full diags if this may help.

$ cygcheck.exe -s

Cygwin Configuration Diagnostics
Current System Time: Thu May 15 16:15:02 2014

Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1
[...]

[tjarratt]

Thanks for confirming. I don't know when this will be fixed, but it is a known bug.

For what it's worth, our supported clients on windows are powershell and cmd.exe

You can also use the 'cf auth' command to authenticate non-interactively.

Sent From A Very Small Keyboard

On May 15, 2014, at 8:18, Guillaume Berche notifications@github.com wrote:

You're right, it works properly with cmd.exe but fails within cygwin even if -u is not specified

$ cf login -a https://api.run.pivotal.io -o myorg
API endpoint: https://api.run.pivotal.io

Email> user@domain.com
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
Authenticating...
Credentials were rejected, please try again.
FAILED
Unable to authenticate.

API endpoint: https://api.run.pivotal.io (API version: 2.4.0)
Not logged in. Use 'cf.exe login' to log in.
I'm using cygin on win7

$ cygcheck.exe -V
cygcheck (cygwin) 1.7.27
System Checker for Cygwin
Copyright (C) 1998 - 2013 Red Hat, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I can send you privately the output of $ cygcheck.exe -s with full diags if this may help.

$ cygcheck.exe -s

Cygwin Configuration Diagnostics
Current System Time: Thu May 15 16:15:02 2014

Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1
[...]
—
Reply to this email directly or view it on GitHub.

[mbhave]

@gberche-orange @tjarratt We are closing this issue for now because Cygwin is not supported currently. There is a story in the CLI tracker project for this feature which can be found here.

Thanks,
CF Community Pair (@mbhave, @stupakov)

[tjarratt]

Also it seems that cygwin is not currently a supported environment for Windows. A little surprising, but makes it easier to explain why this doesn't work.

[robdimsdale]

+1 on this issue. Is cywgin still unsupported? Also, the tracker link is broken - was the story deleted?

[hagemt]

Another +1 here. As for the story, after sign-up, I get: "You are not allowed to view the requested page."

[hao5ang]

+1

[maximilien]

-1 for cygwin or windows...

I kid, I kid, of course. We <3 our Windows users. Cheers.

[gberche-orange]

For windows users, a bash shell with productive features (searching in the history, clipboard cut/paste, completion on file path, alias to set CF_HOME to switch among CF instances...), makes a real difference in term of productivity when using the CF CLI.

I currently work around this issue using cf auth login pwd instead of cf login.

[dhudici]

+1

[michaellihs]

+1 for implementing Cygwin support or at least providing a workaround with the current "bug"