<gwillen>
Can someone remind me where the instructions for using Davros with the OwnCloud client are?
<gwillen>
I have it set up somehow but I can't find anything to remind me how I did it.
<gwillen>
Also, do I remember someone saying that Davros won't work with OwnCloud for Android? If not can someone tell me a little about why?
<gwillen>
(and whether that's in the works?)
heliostatic has joined #sandstorm
<zarvox>
hi gwillen! merry christmas!
<gwillen>
Hey zarvox! :-)
<gwillen>
I swear my configuration question is a legitimate chain of yakshaves away from celebrating the holiday. ;-)
<zarvox>
I think Davros itself has instructions for setting up desktop sync in the app, but it's basically "install the owncloud sync client, then add a particular URL/username/password"
<gwillen>
do you know how I get to those instructions, zarvox?
<gwillen>
oh, I'm stupid
<zarvox>
menu -> clients :)
<gwillen>
you click 'clients' and they're right next to the client download links
<gwillen>
yeah, thanks
<zarvox>
if you're on Linux, you can likely use your package manager's version
<gwillen>
okay, let's try that in the android app and see what breaks
<zarvox>
I /think/ the current state of things is "no one (with the possible exception of mnutt) has looked in detail at making owncloud-android work with Davros yet"
<gwillen>
yeah, the pull you mentioned has discussion of the bug that needs to be fixed on the client end
<zarvox>
that's for the iOS app though
<zarvox>
I think the android app is a completely separate codebase
<gwillen>
oh, hm
<gwillen>
it seems like it's having a similar problem with the HTTP Basic auth though
<zarvox>
and I vaguely remember mnutt saying he doesn't have an android device, so he hadn't looked at it much?
<zarvox>
yeah
* gwillen
nods
<gwillen>
well
<gwillen>
I'm on alpha
<gwillen>
do you know if alpha has pull 1141 uet?
<gwillen>
yet*
<zarvox>
definitely
<gwillen>
okay
<zarvox>
months ago
<gwillen>
then I assume there's something going wrong with the http basic handling in the app
<zarvox>
Yeah, that sounds likely.
<gwillen>
with the appropriate credentials in the URL, it still says 'Wrong username or password'
<gwillen>
not at the username/password stage but at the URL checking stage
<zarvox>
So, maybe it's not actually sending the username/password from the URL.
<gwillen>
yeah, I could believe that
<gwillen>
I assume the error it's giving is just quoted from the http error
|jemc| has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
|jemc| has quit [Ping timeout: 260 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
dlitz has quit [Remote host closed the connection]
|jemc| has joined #sandstorm
dlitz has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
heliostatic has quit [Ping timeout: 265 seconds]
|jemc| has quit [Ping timeout: 240 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 246 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 256 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
|jemc| has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
<gwillen>
zarvox: hm, so I'm fiddling with this trying to figure it out
<gwillen>
so the first thing I did was grab my Davros server URL, which has the form "http://sandstorm:<password>@alpha-api.sandstorm.io/" and wgot that
<gwillen>
and wget says "> Authorization: Basic <based64'ed sandstorm:password>"
<gwillen>
but sandstorm says Missing or invalid authorization header.
<gwillen>
so I'm trying to understand what I should be doing here to test this and reproduce the successful path
<asheesh>
gwillen: Yo
<asheesh>
For some reason I'm awake for a sec
<asheesh>
FWIW http vs https
<asheesh>
Hopefully you mean https since iirc alpha is only available over https not http
<asheesh>
http might cause a redirect
<asheesh>
But I'll try what you just tried too
<asheesh>
Oh gwillen wget is not on the user agent whitelist.
<asheesh>
One sec
<gwillen>
oh heeeeh
<gwillen>
that might explain the OwnCloud android app all on its own...
<gwillen>
remind me why there is a user agent whitelist
<gwillen>
(and why the response is "no authorization header" when I supplied one and it should really say "your useragent is not on the whitelist")
<asheesh>
Also I wonder, can't we "just" use content-security-policy to block all inline JS?
<asheesh>
But anyway.
<gwillen>
hmm doesn't that pull totally break us?
<gwillen>
because aren't we doing some weird thing where we have one password in the URL and then a completely different one in the password field
<gwillen>
for reasons unclear to me
<gwillen>
but seeming like we have to first use HTTP basic to get in, and then separately authenticate to Darvros
<gwillen>
Davros*
<asheesh>
The fact that they're different is an accident; they have the same permissions, it's just that they're generated independently so happen to be different.
<gwillen>
huh
<gwillen>
should they be interchangeable?
<asheesh>
Yeah I think so.
<asheesh>
Let me check
<gwillen>
why do the instructions put credentials BOTH in the URL _and_ in the credential boxes?
<gwillen>
that doesn't seem like something you'd do by accident
<asheesh>
Because of UX issues with basic auth in the owncloud apps
<asheesh>
I should probably sleep rather than make relatively little sense
<zarvox>
gwillen: yeah, so in an ideal world, the owncloud apps would read the basic auth username and password from the initial url, and then just use those, or at least autocomplete the form fields
<zarvox>
we need HTTP basic auth to get in to check the version number, because Owncloud assumes that's public, but we can't route api endpoint requests to the right grain without being webkey-authenticated
<gwillen>
ah, hm
<zarvox>
Once you enter the password all the times, does the android app work?
<gwillen>
zarvox: no
<gwillen>
zarvox: afaict it ignores the username and password boxes and refuses to proceed if it doesn't like the URL
<gwillen>
and I think it's ignoring the basic auth stuff in the URL
<gwillen>
and so failing to believe there's a real owncloud server at it
<zarvox>
ahhh, that'd do it
<gwillen>
12-26 00:06:37.802 3330 3347 E GetRemoteStatusOperation: Connection check at https://sandstorm:<...>@alpha-api.sandstorm.io: Operation finished with HTTP status code 401 (fail)
<gwillen>
and then I put the same url into curl (setting the user-agent) and it succeeds with 200
<gwillen>
so either it's not using the basic auth in the URL, or it's using an unexpected user-agent
<gwillen>
zarvox: hm, ultimately it all ends up in org.apache.commons.httpclient
xet7 has joined #sandstorm
<zarvox>
probably commons httpclient doesn't use the username/password from the URL or something
<zarvox>
I should sleep though
<gwillen>
I can't figure out from anything I've read whether it does or not
<gwillen>
heh, yeah, me also
gambatte has joined #sandstorm
amyers has joined #sandstorm
Kamilion has quit [Ping timeout: 260 seconds]
dlitz has quit [Ping timeout: 265 seconds]
dlitz has joined #sandstorm
Kamilion has joined #sandstorm
amyers has quit [Ping timeout: 260 seconds]
|jemc| has joined #sandstorm
heliostatic has joined #sandstorm
heliostatic has quit [Read error: Connection reset by peer]