I’m still not giving up 
Right now reverse engineering their authorization stuff so it might still be doable from inside the RoPieee webpage.
5 Likes
I respect your tenacity.
Sounds like you’re ok with the idea of providing a place on the RoPieee web page for the user to cut/paste the claim code?
No… I’ve found a way to request a claim code. To be able to do that you need to provide your username, password and verification code.
2 Likes
I’m probably misunderstanding the implementation issues from the developer perspective … as a user I’d prefer to not give RoPieee my username/password/etc, but I don’t mind entering a claim code (which is exceedingly easy for a user to get/copy/paste)
Yeah it’s an implementation detail. The claim code is basically part of the authorization flow: you need to explicitly grant access to the device (RoPieeeXL) to be able to connect to your Plex server. For that it needs to know who you are etc.
So this is a 2FA kinda flow: you need to login (or are logged in), you can ask for a claim code and the software uses that to identifiy itself.
This is fairly normal (basically Roon does something similar), but unfortunately Plex requires you to enter the claim code on the command-line, so in a shell. And that’s far from user friendly of course and for me a definitive no-go. It is waayyy to technical for a lot of users and it requires shell access: something RoPieee does not (and will not) provide.
So my search is about a way where a user needs to fill in certain information in RoPieee’s web interface, and with that information RoPieee fetches the claim code automagically.
Still unsure if this is going to work: getting the claim code is not the problem (any more), but getting the Plexamp software to believe that it’s all ready to go is.
Anyhow, the journey continues. And no worries: I’ll only release this if it makes sense, works reliably and safe.
9 Likes
new version (4.7.0) just released … it can now read the claim token (and player name) from an environment variable … hope this helps enable the authorization flow in RoPieee 
6 Likes
Hi,
Any pointer to documentation about this?
I want to play around with it.
Thanks
Only saw the Release notes.
- Headless: Optionally read player name from environment variable during claim.
- Headless: Optionally read claim token from PLEXAMP_CLAIM_TOKEN env var.
1 Like
Hmmm… that gives a hard error: Error exchanging claim token.
Why did they make this so difficult? 
just sent you some notes on a flow that works for me
Did this lead to any success? I‘m just curious. 
‘Success’ is a big word 
But there is progress. As least the Plex team has made the claim sequence a little bit more friendly for OS’ses like RoPieee.
I’ll keep you posted, still WIP.
4 Likes
Quick update:
Basic stuff works. So for now it seems that this will land in the coming release, unless I hit a blocking issue the coming weeks.
Thanks
6 Likes