Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ampache: also accept authentication in "ssid" key #590

Merged
merged 2 commits into from Oct 22, 2017

Conversation

youknow0
Copy link
Contributor

Until now, we only accepted the authentication token in the "auth"
key. This is the same as in Ampache.

However, for the URL of a song, Ampache passes the authentication
token in the "ssid" key. Some clients expect this key to have
this name, for example the Ampache Plugin for Rhythmbox, as shipped
with Ubuntu.

After this change, Rhythmbox works fine.

There is also a client-side fix for this problem:
lotan/rhythmbox-ampache@0d233e3

Until now, we only accepted the authentication token in the "auth"
key. This is the same as in Ampache.

However, for the URL of a song, Ampache passes the authentication
token in the "ssid" key. Some clients expect this key to have
this name, for example the Ampache Plugin for Rhythmbox, as shipped
with Ubuntu.

After this change, Rhythmbox works fine.

There is also a client-side fix for this problem:
<lotan/rhythmbox-ampache@0d233e3>
@paulijar
Copy link
Collaborator

Okay, makes sense. Please follow the project style guide and indent with tabs instead of spaces.

@paulijar
Copy link
Collaborator

@youknow0 I can merge this PR once you fix the indentations.

@youknow0
Copy link
Contributor Author

Sorry, I am a little busy right now. Indents should be fixed now.

@scrutinizer-notifier
Copy link

The inspection completed: 1 updated code elements

@paulijar
Copy link
Collaborator

Thanks!

@paulijar paulijar merged commit 5417c8e into owncloud:master Oct 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants