ID: 23833
User updated by: pm dot aubertel at free dot fr
Reported By: pm dot aubertel at free dot fr
Status: Bogus
Bug Type: Ingres II related
Operating System: Solaris 2.8
PHP Version: 4.3.2RC4
New Comment:
Hi, I'm not an Ingres specialist but I think the security
configuration is more related to the server.
Use the "cbf" utility and restart Ingres.
Previous Comments:
------------------------------------------------------------------------
[2003-10-21 03:32:18] min dot zou at st dot com
Hi, I have exactly the same problem with php-4.2.2.
I have changed the "config.dat" on ingres client side as suggested.
However, it still doesn't seem to work.
May I know if the change has to be made on server side ?
------------------------------------------------------------------------
[2003-07-16 14:12:35] [EMAIL PROTECTED]
Obviously not any PHP bug then -> bogus.
------------------------------------------------------------------------
[2003-07-16 10:14:09] pm dot aubertel at free dot fr
I figured out what was wrong with the connexion.
After searching in Google for "E_GC1008_INVALID_USER",
I have found a post in the comp.databases.ingres forum
explaining a modification to do in Ingres.
It is related to Ingres security.
I had to modify the "config.dat" file in Ingres
using cbf. This is what I changed:
ii.<hostname>.gcf.mech.null.enabled: false -> true
ii.<hostname>.gcf.security_mechanism: ingres -> null
After that, I bounced Ingres and the php code worked.
------------------------------------------------------------------------
[2003-07-15 02:25:24] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-07-09 15:54:10] [EMAIL PROTECTED]
Did you find any reasons why the sample program works and PHP not..?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/23833
--
Edit this bug report at http://bugs.php.net/?id=23833&edit=1
