redirect-uri and provider differences about ring-oauth2 HOT 4 CLOSED

What does the redirect-uri do?

It's the URI that the authorization server uses to send the user back to the your app. In the OAuth 2.0 specification it's called the "redirection endpoint URI".

The URI is handled by the middleware itself, receiving the token and adding it to the session. When it's done, it redirects the user again to the landing URI.

It appears that each provider returns different data sets and that this library doesn't seem to handle the POST back to get the actual data I'm trying to access (email read only in my scenario).

No, but it should be straightforward. You need to add the token to a header on your POST request, like:

Authorization: Bearer <token>

How that's done depends on which HTTP client library you're using.

from ring-oauth2.

Thanks for the quick response. So is there no way to do processing inside the redirect-uri handler? It appears to just get auto-handled by ring-oauth2? I'm just trying to figure out where in my code I would do the POST back with the Bearer token. It seems a bit odd to me to do that in the landing-uri but that may just be because I think of a "landing" page to be where you want to redirect the user after all the oauth processing work is done vs having different landing-uri's for each provider that do POST's back to the provider and then render something to the browser.

e.g. this code never gets to the debug println statement

;; github oauth2
(defn oauth-github-launch [])

(defn oauth-github-callback [request]
  (println "got here")
  )


(defroutes github-oauth2-routes
  (GET "/auth/github" []
       (oauth-github-launch))
  (GET "/auth/github/callback" request
       (oauth-github-callback request)))

I have this in my middleware

(mount/defstate app
  :start
  (middleware/wrap-base
   (routes
    (-> #'home-routes
        (wrap-routes middleware/wrap-csrf)
        (wrap-routes middleware/wrap-formats))
    (-> #'github-oauth2-routes
        (wrap-routes middleware/wrap-csrf)
        (wrap-routes middleware/wrap-formats)
        (wrap-routes middleware/wrap-github-oauth2))

from ring-oauth2.

I'm just trying to figure out where in my code I would do the POST back with the Bearer token.

Put it in the handler for the landing URI.

There is an issue #10 which suggests adding a success handler that would be executed by the redirect URI, but aside from skipping a redirect the result would be the same as putting the logic in the landing URI instead.

from ring-oauth2.

OK cool. Many thanks!!

from ring-oauth2.