-
Notifications
You must be signed in to change notification settings - Fork 20
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 token based authentication instead of password. #311
Comments
I've verified that we can do this: sbtools::set_endpoint("production")
authenticate_sb("[email protected]")
token <- sbtools:::pkg.env$keycloak_token
token <- token[names(token) %in% c("access_token", "refresh_token")]
token <- jsonlite::toJSON(token)
sbtools:::initialize_keycloack_env(token) Struggling to test this out on beta sciencebase for some reason. |
We were having issues with beta until yesterday afternoon- have you tried
since then?
…On Thu, Oct 26, 2023 at 7:19 AM David Blodgett ***@***.***> wrote:
I've verified that we can do this:
sbtools::set_endpoint("production")
***@***.***")
token <- sbtools:::pkg.env$keycloak_token
token <- token[names(token) %in% c("access_token", "refresh_token")]
token <- jsonlite::toJSON(token)
sbtools:::initialize_keycloack_env(token)
Struggling to test this out on beta sciencebase for some reason.
—
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMBD57CWT66R6BFLRGQWHDYBJPMZAVCNFSM6AAAAAA54N3TMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGEYDSNRRGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
This was last night. I have a lead that the token I get from beta is actually bound to a different keycloak client id than the one I create with authenticate_sb(). I still need to test that out though. |
Merged
This is done in in #314 -- there's plenty more to clean up, but the basics are all in place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As implemented here: https://github.com/DOI-USGS/sciencebasepy/tree/kc_auth we need to support keycloak based authentication.
The text was updated successfully, but these errors were encountered: