Mercurial > prosody-modules
view mod_auth_external_insecure/examples/go/prosody-auth-example/main.go @ 5682:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 29 Oct 2023 11:30:49 +0100 |
parents | f84ede3e9e3b |
children |
line wrap: on
line source
package main import "fmt" import "bufio" import "os" import "strings" const ( ACTION = iota USER HOST PASSWORD ) func main() { stdin := bufio.NewScanner(os.Stdin) for stdin.Scan() { parts := strings.SplitN(stdin.Text(), ":", 4) switch parts[ACTION] { case "auth": if parts[USER] == "someone" { fmt.Printf("1\n") continue } default: fmt.Printf("0\n") } } }