-
Notifications
You must be signed in to change notification settings - Fork 113
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
OCM: provider authorizer problems #4791
Comments
When trying to get provider information from Confirming it with
logs on
but somehow this doesn't make sense, since in this file: reva/internal/http/services/wellknown/wellknown.go Lines 74 to 80 in dde65a4
this path has been marked as unprotected with the prefix reva/cmd/revad/runtime/http.go Lines 83 to 90 in dde65a4
|
It turns out that the
This was due to a misconfiguration:
@glpatcern suggested that it should be like:
|
These are my finding about the "open" driver for ocmprovider:
The error happens because of an error probing OCM services at the remote server:
since the provider domain doesn't have
http://
orhttps://
scheme prefix.but if the ocmprovider is set to
json
driver:Reva will read the correct endpoint with
https://
orhttp://
from json file and connect to it.The text was updated successfully, but these errors were encountered: