This works just fine, but I have some inconvenience that I feel now that I should solve with a different approach. For example, when the user goes to play one song in that local url, the autheticated user is lost and it has to login again when coming back to the Menu. Also, I find some issues trying to share data or information between both the RS menu and the external resource.
I believe the most logical thing would be to have a screen component where the external resource would be loaded with appropriate parameter. When I take a look at the RS menu I see this may be possible in the routing section:
Where it asks for the URL path component could I say something like “./follow/follow.html” and then add the specific url to the song in the parameters?
Other than this, I have been pointed to JWT but what I have reading I believe this would be a little bit tricky for something that is a resource within the project. I am not sure.
Thank you in advance!