-
Notifications
You must be signed in to change notification settings - Fork 28
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
Support authentication of STAC Catalogs #207
Comments
hi @Samweli , Do you know if QGIS authentication system supports GDAL's It looks like QGIS auths are restricted to specific remote resources (below is from the QGIS doc... but not sure if it's up-to-date) If not, we should still be able to use the framework to get token and put the authorization bearer somewhere GDAL can find it ... |
Hi, @Samweli! Do we need to pass the authentication parameters here? update for clarity pystac_client.Client.open(
<CATALOG_URL>,
headers={"x-functions-key": <TOKEN>}
) From what I can tell, the plugin is not passing any credentials to |
@hrodmn I believe that's the STAC endpoint. You have to pass the parameters from here: Unfortunately for now I am still not able to use OAuth2 |
I opened a fork and made a change that enables API header authentication via the QGIS authentication manager: Right now it would only work for an API Header type of authentication so it's not a complete solution. |
Okay, thanks for clarifications! |
Hi @remicres it currently doesn't supports the handler there is no entry for it in the list of the supported auth methods. |
Hi @hrodmn, as you mentioned at the moment the plugin doesn't support passing authentication parameters to the |
Hi @Samweli thanks for the info. I guess accessing secured assets files is another thing. I am starting to think that this could be done nicely with a secured (i.e. with auth. required) dynamic STAC endpoint returning signed assets URIs. |
The QGIS application provides an authentication framework for different data providers. We need to integrate the plugin so that it works with all types of authentication that are supported by QGIS authentication system.
The UI for this is already in place and it was intended to work from the last release plugin version.
See #124 and #206
The text was updated successfully, but these errors were encountered: