Hey Christian,
Have you had a chance to look into this? Is there any other information I
can get you?
-Zach
On Fri, Aug 15, 2014 at 10:11 PM, Zach Auclair wrote:
> Hi Chris,
>
> The output of the "list-evolutions" command is actually included in my
> last paragrap
ry" ALTER COLUMN "raw_file_url" SET NOT NULL;
ALTER TABLE "scmtools_repository" ADD COLUMN "visible" boolean ;
UPDATE "scmtools_repository" SET "visible" = True WHERE "visible" IS NULL;
ALTER TABLE "scmtools_repository" ALTER CO
and a few
>>> other things. I have a couple hours I can spend right now, so I'll see if
>>> anything stands out.
>>>
>>> Where did those SQL statements come from?
>>>
>>> FWIW, Django Evolution has been around since the 1.0 alphas.
>>&
Hey Christian,
Some of the differences from the stock apache config include:
SetEnvIf Request_URI "^/api/.*$" ignore_kerberos
SetEnvIf Request_URI "^/reviewboard.wsgi/api/.*$" ignore_kerberos
AuthName "Kerberos Login"
AuthType Kerberos
Krb5Keytab /etc/httpd/m
Hey Christian,
To add more debugging context:
* If I use basic auth against the api with an existing service account, I
can than use the sent cookie against the api again.
* If I auth against the kerberos-protected portion, I am then not able to
use the cookie against the api.
Do you have any tho
