Mercurial > prosody-modules
view mod_auth_external_insecure/examples/bash/prosody-auth-example.sh @ 5185:09d6bbd6c8a4
mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow
It's optional and the one stored in the client registration should
really be used instead. RFC 6749 says an URI provided as parameter MUST
be validated against the stored one but does not say how.
Given that the client needs their secret to proceed, it seems fine to
leave this for later.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 02 Mar 2023 22:00:42 +0100 |
parents | f84ede3e9e3b |
children |
line wrap: on
line source
#!/bin/bash IFS=":" AUTH_OK=1 AUTH_FAILED=0 LOGFILE="/var/log/prosody/auth.log" USELOG=false while read ACTION USER HOST PASS ; do [ $USELOG == true ] && { echo "Date: $(date) Action: $ACTION User: $USER Host: $HOST Pass: $PASS" >> $LOGFILE; } case $ACTION in "auth") if [ $USER == "someone" ] ; then echo $AUTH_OK else echo $AUTH_FAILED fi ;; *) echo $AUTH_FAILED ;; esac done