API Key Code 401 on Check Authentication

jstephens576 · 2016-02-22 03:06:49

If I turn on htaccess authentication through my dreamhost admin "goodies" - It breaks the authentication in publisher. I get an error "Error performing function. (Code: 401)" when I enable the security, works fine when I disable it. Is there a user name I can add to the "user accounts for this area" to allow htaccess (it requires username password) to allow the publisher service to update? Is there something else I need to set? if so, what?
Thanks

Daniel Leu · 2016-02-22 10:15:43

How about adding an .htaccess file w/o access control inside the ttg-be folder? This way you have access control for your site, but disable it for the ttg-be directory where none of your images/content resides?

jstephens576 · 2016-02-22 11:02:31

I understand that would probably be a good solution - Here is the current contents of the .htaccess file in the top level directory
### Generated by Dreamhost. DO NOT modify!!! ###
AuthType Basic
AuthUserFile /home/stephens576/stephens-gallery.com/.htpasswd
AuthName "Members Area"
require valid-user
################################################

I have limited knowledge of this. Can you advise on what the .htaccess file content should be in the ttg-be directory?
Thanks again

Ben · 2016-02-22 19:07:53

Publisher doesn't provide a place to add htaccess authentication credentials. The only location within ttg-be that needs protection is ttg-be/data. That directory should already have in it an .htaccess file with the following contents:

Deny from all
Options All -Indexes

You can test that this is working for you by browsing to /ttg-be/data on your server. You should receive a 503 forbidden. Adding an html file into the directory, e.g. /ttg-be/data/test.html should also result in a 503.

If you really want to add .htaccess to ttg-be, do so in directories other than /ttg-be/publisher. e.g. /ttg-be/admin/

Daniel Leu · 2016-02-23 04:50:27

Ben, the reason to add an .htaccess to ttg-be is because jstephens576 wants to protect his main site. Since Publisher doesn't support authentication credentials, this has to be disabled for ttg-be.

Daniel Leu · 2016-02-23 04:55:34

jstephens576,

The new .htaccces file in ttg-be should just contain this:

Satisfy Any

Or in case you are running on apache 2.4

Require all granted

Once you have added this and Publisher works, check that you can't access /ttg-be/data.

Ben · 2016-02-23 05:27:30

Placing that .htaccess file withing ttg-be/publisher should fix the Publisher authentication without also removing htpasswd protection from the rest of ttg-be (less data).

Ben · 2016-02-23 07:00:46

I've added basic HTTP authentication support in the Publisher LR plugin. It works well in my testing. Let me know if you're keen on trying it out and I will email you a copy.

jstephens576 · 2016-02-27 22:39:07

Thanks for the discussion - Ben - I will try your advice below and would be the willing to give for update for the LR plugin a try. email jstephens576@gmail.com
Thanks!

jstephens576 · 2016-02-29 10:53:37

dl - your .htaccess in the publisher directory above worked well. data still protected
Thank you.

Community @ The Turning Gate

#1 2016-02-22 03:06:49

API Key Code 401 on Check Authentication

#2 2016-02-22 10:15:43

Re: API Key Code 401 on Check Authentication

#3 2016-02-22 11:02:31

Re: API Key Code 401 on Check Authentication

#4 2016-02-22 19:07:53

Re: API Key Code 401 on Check Authentication

#5 2016-02-23 04:50:27

Re: API Key Code 401 on Check Authentication

#6 2016-02-23 04:55:34

Re: API Key Code 401 on Check Authentication

#7 2016-02-23 05:27:30

Re: API Key Code 401 on Check Authentication

#8 2016-02-23 07:00:46

Re: API Key Code 401 on Check Authentication

#9 2016-02-27 22:39:07

Re: API Key Code 401 on Check Authentication

#10 2016-02-29 10:53:37

Re: API Key Code 401 on Check Authentication

Board footer