So it looks like I'll have to have a single bridge that decides which auth
method to use and then authenticates. I was hoping there was some way to do
that when defining the routes, such as
$bridge1->get("/resource")->to(...); # if it fails continue
$bridge2->get("/resource")->to(...);
or some something like that
On Saturday, August 23, 2014 2:17:23 PM UTC-4, Justin Hawkins wrote:
>
>
> On 23 Aug 2014, at 3:44 am, Richard Sugg <[email protected] <javascript:>>
> wrote:
>
> > Anyone have any patterns they have followed in this situation? I realize
> that some may have objections to my implementation, but I am developing an
> internally-used corporate website, so I don't have leeway in the matter. I
> know how I *could* do this, but would be happy to hear others' thoughts on
> implementation first.
>
> If you want automated tools to have access, providing a per-user API key
> (which can be generated/changed/revoked when appropriate) is a common way
> of providing access to non-interactive “users”.
>
> - Justin
>
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
