weavejester/ring-oauth2

Issues

• Help getting started with ring-oauth2 and Luminus

  #17 opened 6 months ago by perrygeo
  2

• 400 "No authorization code" on callback, even though I can see code in URL string

  #43 opened 6 months ago by njerig
  4

• Unclear error messages

  #53 opened 6 months ago by whamtet
  1

• 3-arity Ring handler for use with Ring async

  #54 opened 6 months ago by enspritz
  1

• Supporting multiple profiles for the same provider?

  #52 opened a year ago by lukaszkorecki
  5

• clj-http now requires cheshire 5.9.0

  #46 opened a year ago by jamiepratt
  1

• No reader function for tag object when using cookie store

  #27 opened a year ago by Heliosmaster
  10

• Middelware does not work with Facebook?

  #49 opened a year ago by gerdint
  1

• Support for dynamic authorization URL params

  #41 opened 4 years ago by sbauch
  7

• Allow supplying custom success, error handlers

  #10 opened 7 years ago by kaosko
  5

• Internal Server Error/404 on callback from Youtube API

  #24 opened 6 years ago by ZadenRB
  1

• Implicit dependencies on other middelware

  #12 opened 7 years ago by ingesolvoll
  5

• Requesting a new release with redirect handler support

  #44 opened 3 years ago by ajitj
  1

• Works when deployed to "/" but 404s when run with a context path

  #35 opened 4 years ago by yatesco
  2

• refresh token functionality

  #40 opened 4 years ago by Yunfeng-Song
  1

• Logout Flow

  #38 opened 4 years ago by MyriaCore
  2

• Help: how to allow a local administrator to bypass?

  #34 opened 5 years ago by yatesco
  2

• Is the example `ring-defaults` missing the actual handler in README.md?

  #32 opened 5 years ago by yatesco
  1

• cannot get the token

  #30 opened 5 years ago by bongistan
  4

• Enhancement: configure middleware for the internal POST calls

  #25 opened 6 years ago by Kah0ona
  2

• Scary error when forgetting `client_id` or `client_secret`

  #19 opened 6 years ago by AndreaCrotti
  1

• redirect-uri and provider differences

  #18 opened 7 years ago by earthtrip
  4

• X-Forwarded-* headers are not used for resolving the URI

  #15 opened 7 years ago by kaosko
  1

• How to retrieve the access token received from the Provider ?

  #14 opened 7 years ago by bcambel
  2

• expires_in is not a number, coming from Microsoft Azure

  #13 opened 7 years ago by ingesolvoll
  1