-
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
Update deps 2020 07 22 #409
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Looking at webui tests, one can see that the login is failing on CI. Might be related to changes in ocis-accounts, needs investigation. @individual-it did you already play around with current ocis-accounts master on CI? Are there known issues with web ui logins for tests? |
the tests are using the build in phoenix and using that I cannot login neither with the test users (einstein) not with LDAP users.
log logs in the ocis console with LDAP I get redirected after the kopano page, but the request to https://localhost:9200/ocs/v1.php/cloud/capabilities?format=json get a HTTP 500 response and I end up on a login error page. ocis log output:
CC @butonic |
We probably should execute go mod tidy at the end |
87d945c
to
5f97bc1
Compare
b9d6dac
to
a2a6e28
Compare
|
7a3cb9b
to
0b3aa07
Compare
9a1ce4b
to
d4f2c93
Compare
|
The problem is that we are provisioning test users using ldap. thas leads to a disconnect beween usernames (in ldap) and the uuid that is generated by the accounts service. As a result, the api tests (which are using basic auth) will resolve the login to the uid attribute in ldap, e.g. We have several short term options:
Long term solution: implment an ocis-accounts-ldap service that is persists users in ldap directly. I would vote for implementing the ocs provisioning api, as we need that anyway.
|
@individual-it since the most recent commit to this PR (21db7ed), we now have the important bits of the user provisioning API in ocis-ocs. Could you please check, if you can make use of this for provisioning users in tests? Afaik you already do this for oc10. Maybe it is a quick win to do the same in ocis now. Please check if the provided API is sufficient for your needs - and if not, what else you need. |
@kulmann also needs owncloud/ocis-accounts#70 but the web ui tests fail there |
@individual-it btw the provisioning endpoint for users in ocis allows you to set the |
@kulmann @butonic issues with the new provisioning API
|
current issues:
|
basic auth is not checked the second time, when the username is capital case: both requests response with content if first the correct password was given AND the userid begins with a capital case 🙀 |
@individual-it can you post instructions how to run the testsuite with the user provisioning api here so we can continue when you need to leave. We found a problem in reva: cs3org/reva#1033 that requires some coding to properly look up the userid ... |
|
PR for disabling randomly failing Phoenix test owncloud/web#3955 |
|
- ocis-ocs v0.2.0 - ocis-pkg/v2 v2.3.0 - ocis-proxy v0.6.0 - ocis-reva v0.12.0 - ocis-settings v0.1.0 - ocis-store v0.1.1 - ocis-thumbnails v0.3.0
Updated ocis-phoenix to 0.11.0 (includes phoenix 0.14.0). |
@api @issue-ocis-187 | ||
Feature: previews of files downloaded through the webdav API |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did these get deleted?
I don't see where previews was fixed in core - expected-failures.txt
has a whole list of core scenarios apiWebdavPreviews/previews.feature:*
that are still expected failures.
In a separate PR I can try what happens if these "bug demo scenarios" are put back.
I pushed 2 commits to tidy up some doc and comments in Are we going to squash the 84 commits before merging? |
Let's not squash these, keep them as a tribute and reminder of our struggles. |
Any objections to merging this PR now ? I think we're already far enough down the road that it doesn't make sense to hold this any more. If we find any regressions in EOS we'll fix these separately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
[Tests-Only] Bump commit id for oC10APIAcceptanceTests
Disclaimer
For the purpose of this upcoming release we will do the process backwards without tagging. We will point dependencies to its latest master at a given point on time, Once the
ocis
release is complete, tags will be added to each extension.Involved steps are:
Releases:
This PR can be used to test downloads with pre-signed urls. There is a manual step involved for phoenix:
OCIS_LOG_LEVEL=debug PHOENIX_ASSET_PATH=/path/to/phoenix/dist/ go run cmd/ocis/main.go server
Debugging failing tests
Debugging failing tests
Technical debt / future tasks to schedule
Tickets raised for remaining work based on this: