-
Notifications
You must be signed in to change notification settings - Fork 5
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 for direct access flow will be removed #34
Comments
Flow would be something like:
You temporarily save Finally, you can get the access token with
I guess it doesn't make sense to use a confidential client here, but let me know what you think |
@asergios is this part:
absolutely necessary ? [I mean the |
Hello @tngTUDOR, thanks for your answer and sorry for my late reply. |
ack @asergios . |
It won't be possible with the use of username/password. An API key should be the future alternative. I am open to suggestions tho. |
Speaking from a group of users that don't use activity browser too much, I have to say that the idea of an API Key is very very very compelling. |
I understand. I did not consider this, let me get back to you on this topic. Wdyt? |
* As requested on #34, this sends a different client id to keycloak #34 (comment) Signed-off-by: João Gonçalves <[email protected]>
@asergios I'm not sure we actually use the |
Here's my view of how could things be done, in a way that is useful for GUI and API users:
@asergios , if you already have an implemenatation that we could use for testing, we can |
Hey!
Ecoinvent will remove direct access flow support from their clients.
I believe this will make the interface stop working
ecoinvent_interface/ecoinvent_interface/core.py
Line 98 in dd2b406
I will be delaying this change on PROD for a bit so that alternatives can be discussed here.
Would you be open to implement
Device Authorization Flow
?We are open to create a client for you to use this, I already have a proof of concept too.
I don't know what would be the best approach for you to save the client secret.
The text was updated successfully, but these errors were encountered: