-
Notifications
You must be signed in to change notification settings - Fork 189
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
oCIS - some eos set up problems #257
Comments
when I finally get in through phoenix I see the same issue on the webUI and in the log output:
|
doing a basic-auth PROPFIND shows:
|
fixed on previous releases. |
The following description is based in the commit
f379b270
cd ocis
-> OKmake eos-start
-> everything is pulled and finally it manages to work. I can open thehttps://localhost:9200
after accepting the risk of non-secured siteAfter typing credentials (
einstein:relativity
) i get the following message:Current behaviour: if you give another try, it works. Only failing the first time
Expected: correctly redirected to list of files
the most "scaring" logs are printed during the execution of such action are:
Tested with Firefox 76.0
Then i reach the list of files and i see:
here i see a bunch of logs pretty similar to the previous ones.
Apart of that, i can not do any action:
Expected: i can do actions, create folders, upload stuff etc...
Checks performed:
user is looking up against glauth:
with commands, i can create folders with
but nothing visible on the web client (client issue??)
Tested with Firefox 76.0
The last but not the least affects directly the clients. Please, this is pretty important. Redirection URLs with EOS seems to be hardcoded to
localhost
, so there is no way to connect from client to server under different IP:Current Behaviour:
In regular oCIS it is posible by adding redirect urls with the specific IP. But here, i did not get the way to do the same.
Expected: Clients can complete correctly the authentication/authorization flow by using the IP/name of the server host.
iOS13.4
iPhoneX
ownCloud 1.3.2
The text was updated successfully, but these errors were encountered: