Solved

receiving this error : Client used wrong authentication scheme 'Basic' in request for URI /index.php

Posted on 2014-07-31
5
1,701 Views
Last Modified: 2014-08-06
this is the error message when someone is posting to our site. The error is: Client used wrong authentication scheme 'Basic' in request for URI /index.php. Here are some logs for your review:

Not sure if it has something to do with the SSL or not or does it need to be hard coded in the Apache file?

scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:01:45 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:02:44 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:03:16 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:05:46 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:06:22 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:07:21 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:07:44 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
[Thu Jul 31 16:07:47 2014] [notice] caught SIGTERM, shutting down
[Thu Jul 31 16:07:51 2014] [warn] RSA server certificate CommonName (CN) `staging.qstreetmeds.com' does NOT match server name!?
[Thu Jul 31 16:07:51 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Thu Jul 31 16:07:51 2014] [warn] RSA server certificate CommonName (CN) `staging.qstreetmeds.com' does NOT match server name!?
[Thu Jul 31 16:07:51 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Thu Jul 31 16:07:51 2014] [notice] Apache/2.2.26 (Unix) mod_wsgi/3.3 Python/2.7.5 mod_ssl/2.2.26 OpenSSL/0.9.8y DAV/2 PHP/5.4.24 configured -- resuming normal operations
[Thu Jul 31 16:08:49 2014] [client 69.25.46.11] mod_digest_apple: Client used wrong authentication scheme 'Basic' in request for URI /index.php
0
Comment
Question by:Steve Lizardi
  • 3
5 Comments
 
LVL 109

Expert Comment

by:Ray Paseur
ID: 40232969
Can you please give us a little more to go on?  SSCCE.  The URL, the source code of the program that generated the messages, the client input that triggered the messages -- things like that will give us a chance to help.
0
 
LVL 17

Expert Comment

by:Chris Harte
ID: 40234054
A bit of googling and the only thing I could come up with was owncloud. You need to disable 'Basic' authentication.

http://forum.owncloud.org/viewtopic.php?t=8073

(As Ray pointed out, without a point of reference this is just a guess.
Or, to quote Lord Blackadder,
'No, just a wild stab in the dark which is incidentally what you'll be getting if you don't start being a bit more helpful').
0
 

Author Comment

by:Steve Lizardi
ID: 40235057
Well I disabled the module and now I get more errors. It was working fine before. This is on a mac server 10.9. the vendor uses basic authentication in windows. so what is the difference on the mac server? These are the error logs after I made the change module.

[Thu Jul 31 16:39:58 2014] [notice] Apache/2.2.26 (Unix) mod_wsgi/3.3 Python/2.7.5 mod_ssl/2.2.26 OpenSSL/0.9.8y DAV/2 PHP/5.4.24 configured -- resuming normal operations [Thu Jul 31 16:40:01 2014] [notice] caught SIGTERM, shutting down [Thu Jul 31 16:40:06 2014] [warn] RSA server certificate CommonName (CN) `staging.qstreetmeds.com' does NOT match server name!?
[Thu Jul 31 16:40:06 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) [Thu Jul 31 16:40:06 2014] [warn] RSA server certificate CommonName (CN) `staging.qstreetmeds.com' does NOT match server name!?
[Thu Jul 31 16:40:06 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) [Thu Jul 31 16:40:06 2014] [notice] Apache/2.2.26 (Unix) mod_wsgi/3.3 Python/2.7.5 mod_ssl/2.2.26 OpenSSL/0.9.8y DAV/2 PHP/5.4.24 configured -- resuming normal operations [Thu Jul 31 16:43:15 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Thu Jul 31 16:45:08 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Thu Jul 31 16:46:08 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Thu Jul 31 16:51:08 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Thu Jul 31 16:53:15 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Thu Jul 31 17:01:09 2014] [crit] [client 69.25.46.11] configuration error:  couldn't check user.  Check your authn provider!: /index.php [Fri Aug 01 01:13:29 2014] [crit] [client 184.73.137.39] configuration error:  couldn't check user.  Check your authn provider!: / [Fri Aug 01 08:25:19 2014] [crit] [client 87.114.124.113] configuration error:  couldn't check user.  Check your authn provider!: /index.php, referer: https://www.google.com/search?q=staging.qstreetmeds.com&num=30&newwindow=1&filter=0&biw=1235&bih=935
[Fri Aug 01 08:25:19 2014] [crit] [client 87.114.124.113] configuration error:  couldn't check user.  Check your authn provider!: /favicon.ico, referer: https://staging.qstreetmeds.com/index.php
[Fri Aug 01 08:25:24 2014] [crit] [client 87.114.124.113] configuration error:  couldn't check user.  Check your authn provider!: /, referer: https://www.google.com/search?q=staging.qstreetmeds.com&num=30&newwindow=1&filter=0&biw=1235&bih=935
[Fri Aug 01 09:14:47 2014] [crit] [client 186.125.3.31] configuration error:  couldn't check user.  Check your authn provider!: / [Fri Aug 01 11:25:04 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /w00tw00t.at.blackhats.romanian.anti-sec:)
[Fri Aug 01 11:25:04 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /phpMyAdmin/scripts/setup.php [Fri Aug 01 11:25:05 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /phpmyadmin/scripts/setup.php [Fri Aug 01 11:25:06 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /pma/scripts/setup.php [Fri Aug 01 11:25:06 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /myadmin/scripts/setup.php [Fri Aug 01 11:25:06 2014] [crit] [client 192.3.160.42] configuration error:  couldn't check user.  Check your authn provider!: /MyAdmin/scripts/setup.php

Open in new window

0
 

Accepted Solution

by:
Steve Lizardi earned 0 total points
ID: 40235232
The issue was that the index.php was not selected as the default and disabled the mod_digest_apple in apache. Was able to receive the file.
0
 

Author Closing Comment

by:Steve Lizardi
ID: 40243175
Resolved the issue myself. based on the error message and check the settings to make sure they were all correct.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
Nothing in an HTTP request can be trusted, including HTTP headers and form data.  A form token is a tool that can be used to guard against request forgeries (CSRF).  This article shows an improved approach to form tokens, making it more difficult to…
This tutorial will teach you the core code needed to finalize the addition of a watermark to your image. The viewer will use a small PHP class to learn and create a watermark.
The viewer will learn how to create a basic form using some HTML5 and PHP for later processing. Set up your basic HTML file. Open your form tag and set the method and action attributes.: (CODE) Set up your first few inputs one for the name and …

778 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question