Keystore upload fails - Wrong user name or password

[benjamin_bender2]

Hi SCP community,

I'm trying to upload a keystore using the following command, using my subaccount name as <consumer-account-name> and my S-user ID as <user-id>:

neo upload-keystore --account <consumer-account-name> --application a816462b5:dqmmicro --host hana.ondemand.com --user <user-id> --location dqmm.jks

But when entering my S-user password after executing the command I get an error saying

"ERROR: Error occured while trying to check if the keystore already exist: Wrong user name or password"

Any guidance would be very much appreciated.

Thanks,

Ben

[benjamin_bender2]

Forgot to mention, I can logon SCP with the S-user credentials that I'm using in this command.

[former_member197689]

Hi Benjamin,

Were you able to login to SCP landscape via open-ssh-tunnel? This should be step 1 before you uploaded your key.

Thanks,

Jin

[benjamin_bender2]

Hi Jin,

tried to create a virtual machine for the ssh tunnel, but there I also get a user/password error. Could it be that my user is missing some authorizations on SCP?

Thanks,

Ben

[benjamin_bender2 · Accepted solution]

Thanks Jin for your time today, now it is obvious that the right command for the trial environment has to be the following:

neo upload-keystore --account 'consumer-account-name' --application u23133c2f:dqmmicro --host hanatrial.ondemand.com --user 'user-id' --location dqmm.jks

[benjamin_bender2]

I've also tried it with application u23133c2f as it is a trial account but same result as before.

[former_member197689]

Hi Benjamin,

I see that you are one of of production customers so it is better to open a support ticket for this incident. You use component BC-NEO-SEC-CPG

Thanks,

Jin

If this question is answered from your perspective, then please clicked on the “Accept” link to complete this question.

[benjamin_bender2]

Thanks Jin for your quick answer. This request is not related to any production system, this is why I've raised the question here. Also, my S-user is not authorized to raise support tickets.