Opened 7 months ago

Closed 7 months ago

#3339 closed help (fixed)

Problems logging onto puma

Reported by: scottan Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: PUMA
UM Version:

Description

I'm getting locked out of puma with the error:

Permission denied (publickey).

I think this is down the ssh key and password reset that happened a few months ago - this is the first time I've needed to use Puma since then. I've got an updated password but I can't seem to get onto Puma in the first place to use it, it blocks me with the above error however I log on (from local computer or via other services). I've tried deleting all of the configs for logging into puma in my .ssh directory and set up a new ssh-key for puma following instructions on the website, but I'm still being blocked.

Any help greatly appreciated.

Kind regards,
Scott

Change History (1)

comment:1 Changed 7 months ago by andy

  • Resolution set to fixed
  • Status changed from new to closed

Hi Scott,

Looks like you missed the switch to two factor authentication on PUMA email. If you follow the instructions below we'll get you back on PUMA again.

Cheers
Andy

On 05.06.20 12:30, Andy Heaps wrote:

PUMA access is changing to two factor authentication (2FA) on Tuesday
9th June at 11am so that we can become an ARCHER trusted host.

Getting ready for 2FA for your PUMA account:
1) On the computer you work from type
ssh-keygen -t rsa -b 2048 -C "me@…" -f ~/.ssh/id_rsa_puma
Please use a good and not blank passphrase that you haven’t used before.

2) Email the file ~/.ssh/id_rsa_puma.pub to Andy Heaps
(andy.heaps@…)

3) This key will be put in a system directory on PUMA. When 2FA is
started on Tuesday 9th June at 11am you will receive an email with a
temporary password that you will need to reset on login. Please set a
good new password that you haven’t used anywhere else.

4) After 2FA is started on PUMA you will be required to type in your ssh
passphrase and password to login to PUMA. You can use an ssh-agent on
your local computer to cache the passphrase credentials if you wish.

If you have any issues with logging into PUMA after the change please
raise a ticket on the CMS helpdesk.

Note: See TracTickets for help on using tickets.