MFA already set up for brand new PDI

RobinM1
Tera Contributor

I'm faced with the following issue: after requesting a brand new PDI and installing SAM Pro and Discovery on it via the manage instance section, I'm prompted with a MFA code request while logging into the instance. I haven't set up MFA yet for this instance though and a credentials reset for the admin user via the manage PDI section hasn't resolved the issue.

 

Some additional info:

  • I didn't have the authenticator app enabled for my main SN account (verification through email).
  • Setting up the authenticator app for my main SN account doesn't work either (trying everything at this point)

 

Any thoughts on how to tackle this?
I'm afraid the MFA code it's requesting is from a previous PDI, which I no longer have, and I don't see a way to reset the MFA config.

1 ACCEPTED SOLUTION

Viraj Hudlikar
Tera Sage
Tera Sage

Hello @RobinM1 

 

I had faced this issue for my account during buildagent campaign two times and since there is no support for PDI, so I had released the instance waited for 1 hour and then requested a new PDI. I was also puzzled that how without setting MFA for new PDI it can asked code during first access. 

 

In my opinion it will better if you release existing instance and do get a new instance after some time gap.

 

If my response has helped you, hit the helpful button, and if your concern is solved, do mark my response as correct.

 

Thanks & Regards
Viraj Hudlikar.

View solution in original post

10 REPLIES 10

RaghavSh
Mega Patron

@RobinM1 Try incognito window. I believe for the 1st time you will have an option to setup MFA for new instance using QR code.

 


Raghav
MVP 2023
LinkedIn

RobinM1
Tera Contributor

Unfortunately, the incognito window is also prompting me to already fill in the authenticator code (no QR code).

This is PDI which no one else will have access to , so its not possible to reset MFA from backend.

I would say try releasing ad requesting the new instance.


Raghav
MVP 2023
LinkedIn

RobinM1
Tera Contributor

This is already a brand new instance. My previous one was released and I requested a new one, which resulted in this issue.