• 27 Posts
  • 72 Comments
Joined 3 年前
cake
Cake day: 2023年6月6日

help-circle



















  • That’s bad.

    OAuth supports several types of flows. If I’m not mistaken (I’ve learned a bit more about OAuth since yesterday) you’re describing the Authorization Code Flow – as documented in RFC 6749 (The OAuth 2.0 Authorization Framework), Section 4.1 (Authorization Code Grant):

    That RFC defines many other types of flows that do not require sharing the access keys with a third party, such as the Client Credentials Flow, as documented in RFC 6749 Section 4.4 (Client Credentials Grant):

    The only reason you’d want to use the Authorization Code Flow is if the third party needs your access token for some reason, or if you want to hide the access key from the user agent.

    The problem here is that Stripe is using the wrong flow (the third party doesn’t need the access token, as they claim they never save it anyway). And if keyCloak only supports that one flow, that’s would be a problem too (in this case).











  • maltfield@lemmy.mlOPtoLemmy@lemmy.mlIntro Guide to Lemmy
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 年前

    Suddenly my server started getting thousands of requests per minute and my varnish cache hit rate jumped to 99%. Thank god for varnish!

    Looks like the reddit blackout is #1 on the frontpage of hackernews, and this article is #2.

    I actually posted this article to hackernews, but I never got a single upvote. This isn’t my first time getting on the frontpage of hackernews, but it always happens when someone else reposts my link.

    Can anyone tell me how the fuck hackernews’ algorithm works to where I can’t ever get traction but someone else does after me?