auth role has been a part of Rdbhost since the beginning, but was always a 'ugly step child', less respected than the
reader. This was mostly because I and (inferring from their silence) my clients could not envision clear use-cases for it.
Why would you give a role an authcode, and not trust it enough to require white-listing?
Well, we have made use-cases a bit easier, by making the
auth role a bit easier to use.
Now you can configure the
auth role to have its own password, separate from the
auth authcode. When you make requests using the
auth role, you can include the rolename and password as part of the url, and the server will authenticate the request.
Example, broken into two lines for presentation:
This is particularly useful for webhooks. A webhook is a service that loads a url of you designate, providing it data on an event, in response to events on the web-service's server. For example, github.com supports webhooks to report commits and tickets and such. You can restrict usage of the webhook query to only certain web-services, and limit those web-services to only specific request queries.
You can trust web-services, but only trust them so far.