CDSW CLI - login failed to authenticate on MacOS

[#1]

Hi,

I have been using the cdswctl tool for a while for creating sessions that can be accessed by VS Code from Windows.

Today i tried to create a session from a Mac using the same command and it throws an error complaining that the API key is not valid.   I have checked the key and same key works fine from Windows.

The command i am using is :

./cdswctl login -n USERNAME -u http://cdsw.mydomain.xxxx/ -y APIKEY

Can anyone offer any advice?

Thanks

[#2]

@BubbaBoBobBrain Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our CDSW experts @Gopinath @Mike  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3]

Hi - i am still facing a blocker on this.  Can anyone offer any advice?

A colleague with a Mac has also tried and they get the same error:

Failed to authenticate for user <my user name> using provided API key.

Could it be due to case of the usernames?  In CDSW my username is uppercase and on my mac it is lower case?

I have tried putting my username in the login statement matching the case of my CDSW user.

[#4]

@Scharan Any insights here? Thanks!

[#5]

Hi @BubbaBoBobBrain , you need to include the workspace in your login command, see this page: https://docs.cloudera.com/cdsw/1.10.3/cli-reference/topics/cdsw-login-cdswctl.html

This command worked fine for me:
./cdswctl login -u https://mikes-cdsw.cloudera.com  -n mike -y u8ryf6a2977rfsr8zajesand2jhwoa44

Btw on Mac you usually need to first right click on the cdswcli icon and select "Open" - this will let you open the tool once which lets your mac system trust the application, which it won't do by default since it was downloaded from the internet. After this you can use it as normal.

[#6]

Hi @Mike ,

Thank you for the reply. 

I have already trusted the the cdswctl application.

I can't see much difference between my command and yours?

The error i am getting is related to the API key.  If i remove the API key it prompts me for a password but then fails as we used SSO.

[#7]

Oh weird the first time I read this I didn't see you using the server anywhere. No, the command you are using is correct.

Can you expand on this statement?

>Could it be due to case of the usernames?  In CDSW my username is uppercase and on my mac it is lower case?

The username you are using in the command is the CDSW username, not your mac username.

[#8]

My Mac logon, home dir and the username at the end of the SSH public key is as follows:

a1234567

But in CDSW the username is:

A1234567

I didn't know if this would cause a conflict?  I have tried both A1234567 and a1234567 in the login statement.

[#9]

I am in the office now rather than working remotely via VPN and it has worked ok. 😃

I will try again at home later and see if the VPN was causing an issue.

[#10]

I would expect that you need to use A1234567 as that will be the username which matches the API key.

If the only thing that changed was the VPN... that must be the issue. Perhaps the VPN is blocking ssh access or rewriting some header or something? I'm pretty sure that the error about an invalid API key is not the real error - it likely cannot even get to your CML in the first place. When you get back on VPN, can you try to just cURL your server with and without VPN?