# FastCGI Authorizers with nginx

**URL:** <https://www.ruby-forum.com/t/fastcgi-authorizers-with-nginx/194178>\
**Category:** NGINX\
**Created:** [August 31, 2010, 5:16pm UTC](https://www.ruby-forum.com/t/fastcgi-authorizers-with-nginx/194178 "2010-08-31T17:16:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![iT0m](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a9a28c/32.png) [@iT0m](https://www.ruby-forum.com/u/iT0m)\
**Post date:** [August 31, 2010, 5:16pm UTC](https://www.ruby-forum.com/t/fastcgi-authorizers-with-nginx/194178/1 "2010-08-31T17:16:09Z")

</div>

According to the specification FastCGI supports responders, filters and  
authorizers. Nginx surely supports responders. I’m not sure, if it  
supports filters, but it definitely doesn’t support authorizers. Is  
there a architectural reason behind it, was it simply forgotten, or  
wasn’t it requested?  
We are interested in this feature! Unfortunately we don’t have any C  
knowledge. FastCGI authorizers are necessary if you want to use nginx  
together with shibboleth.

Cheers,  
-Tom

Posted at Nginx Forum:

> **[FastCGI Authorizers with nginx](https://forum.nginx.org/read.php?2,125679,125679#msg-125679)**
>
> According to the specification FastCGI supports responders, filters and authorizers. Nginx surely supports responders. I'm not sure, if it supports filters, but it definitely doesn't support authorizers. Is there a architectural reason behind it, was...

---

<div class="post-metadata">

**Author:** ![iT0m](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a9a28c/32.png) [@iT0m](https://www.ruby-forum.com/u/iT0m)\
**Post date:** [August 31, 2010, 5:47pm UTC](https://www.ruby-forum.com/t/fastcgi-authorizers-with-nginx/194178/2 "2010-08-31T17:47:11Z")

</div>

Hello!

On Tue, Aug 31, 2010 at 11:15:24AM -0400, iT0m wrote:

> According to the specification FastCGI supports responders, filters and  
> authorizers. Nginx surely supports responders. I’m not sure, if it  
> supports filters, but it definitely doesn’t support authorizers. Is  
> there a architectural reason behind it, was it simply forgotten, or  
> wasn’t it requested?  
> We are interested in this feature! Unfortunately we don’t have any C  
> knowledge. FastCGI authorizers are necessary if you want to use nginx  
> together with shibboleth.

FastCGI authorizers aren’t supported (as well as filters), only  
responders.

You may achieve similar effect by using auth request module, see  
here:

> **[ngx\_http\_auth\_request\_module: log](http://mdounin.ru/hg/ngx_http_auth_request_module/)**

Maxim D.