Roon login
Authenticator token is being entered but I am unable to login
macOS
MacBook Pro 2011 build 1359 - remote build 1357
MacBook core Weiss dac
Just can’t login
Ok full story- trying to move core from MacBook to antipodes looks like I setup multi factor protection, and I keep trying to enter token from Authenticator app and it will not accept
When I click on view account info here:
I get this page And I have tried several times to enter this token but it won’t take it. I have successfully entered this code into outlook lately with no issuesI can login with my iphone or different macbook into this community for help (obviously), and I can listen to Roon using other iPhone as remote, and ARC looks like it works.
Core is shown as MacBook, as shown above and is working with Antipodes chosen as endpoint.
I don’t want to try disconnect button as it may disappear and prevent Roon from playing?
Can’t disable Authenticator without logging in with it first! Arg.
@benjamin can someone help me login to my account ?
Hi.
It’s been a few days and you haven’t gotten a response, so I thought I’d try to help.
This quote from your post may help figure out what’s going on:
It sounds like you have Authenticator set up and it’s generating codes that work in Outlook. You’re trying to use those same codes to log into Roon.
Outlook is a Microsoft product/service. If you set Authenticator up to work with Outlook (or M365 or whatever Microsoft product), the codes it generates will be specific to Outlook/Microsoft. This is because each service that you want to use Authenticator with provides a unique value to Authenticator which Authenticator later uses to generate codes. So any code you see generated in Authenticator is the result of a secret value shared between Authenticator and some specific service (every 30 seconds Authenticator generates a new code by essentially doing some math that incorporates the current clock time and that secret value).
To use Authenticator with Roon, you would have had to set it up with its own unique Roon relationship. What this would mean is that in your Authenticator app, you’d see at least two codes being generated side by side - one for Outlook, one for Roon.
The Outlook code will only work with Outlook, the Roon code will only work with Roon.
If you only see Outlook in your Authenticator app, then there is no way any of the codes generated will ever work. It’s not worth trying.
You may want to try going through this “Get In Touch” wizard: Get in touch
If you indicate that you are having a billing or account question, you’ll get to a point where you can indicate that you lost access to Authenticator, and hopefully from there, you can recover access.
Just note that when you do set up Authenticator for Roon, you’ll end up seeing Outlook and Roon in your Authenticator app as I described above.
Hope this helps.
thanks for the response. Yes, that makes alot of sense. I do see the option to scan a QR code for some external account (Roon)- “your account provider will display a QR code” I don’t recall doing this previously when adding this option to Roon, and I don’t know how to scan it now? Anyone know where this QR code can be accessed? Or maybe it was unique to my account- I don’t know.
edit: I see I can also enter the code manually- but what/where is it in Roon?
But I don’t know what you mean by “get in touch” wizard- is that through Microsoft? Or Roon?
Ooops…I forgot to include the link to the “Get in touch” page that has the steps I described.
I edited my post above and added it. Try to go through the flow I described in which you say you lost access to Authenticator. Hopefully that’ll get you to a state where you see and scan a new QR code. Good luck!
Oh that “get in touch” I did do that, that is how this support thread was formed 
I don’t think Roon wants me to make another one.
edit: Ah ha! I do see the authenticator option once I hit the billing and account question, thank you! Done. Response email received, now wait until someone responds
The wonderful and talented Rebeka 
disabled my authenticator app, all is well again. 
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
