What feature would you like?
AirPlay and RAOP shares the same "connection" and uses the same crypto routines. So when streaming to an Apple TV running tvOS (older generations are not affected), the same verification process performed when using play_url needs to be done. A forbidden response is returned now:
2021-05-12 12:34:09 DEBUG [pyatv.raop.rtsp]: Got RTSP response to 0: RtspResponse(code=403, message='Forbidden', headers={'Content-Length': '0', 'Server': 'AirTunes/540.31.41', 'CSeq': '0'}, body=''):
Describe the solution you'd like
On one end, this should be pretty easy as all code is already in place. On another end, it's quite tricky as this means there will be a dependency on airplay for this. I will have to authenticate one connection and use that for RTSP afterwards (which doesn't match current design, but shouldn't be that hard to adhere to). Will have to think about this a bit.
Solution-wise, I would prefer if it just works assuming --airplay-credentials are provided with valid credentials.
Any other information to share?
No
What feature would you like?
AirPlay and RAOP shares the same "connection" and uses the same crypto routines. So when streaming to an Apple TV running tvOS (older generations are not affected), the same verification process performed when using
play_urlneeds to be done. A forbidden response is returned now:Describe the solution you'd like
On one end, this should be pretty easy as all code is already in place. On another end, it's quite tricky as this means there will be a dependency on
airplayfor this. I will have to authenticate one connection and use that for RTSP afterwards (which doesn't match current design, but shouldn't be that hard to adhere to). Will have to think about this a bit.Solution-wise, I would prefer if it just works assuming
--airplay-credentialsare provided with valid credentials.Any other information to share?
No