Windows Security Message

[danielpbarros]

Good afternoon staff,

I have just migrated to the production a system I developed in Apex. Everything happened with great tranquility (until I thank Sérgio for the information) but always users will log in to the system, a Windows security message is sent, where it informs that the XDB server requires a username and password.

I put the user and password and marked to record the credentials, but always asks (the user appears and password due to the marked FLG).

Is there a possibility of not appearing this message?

Hugs,
Daniel.

[stcoutinho]

Hi Daniel,

I did not go through this situation, but I found several forums that describe the solution to this problem.

On one of them https://forums.oracle.com/forums/thread ... ID=2201984 , the forista explains:

On My System Anonymous and XDB Account Were Already Unlocked and Both Used The Same Password.
I Simply Executed The PL / SQL Block That You Can Find Here:
http://www.apexexplorer.com/wp-content/ ... -Issue.pdf
I Bounced The Listener.

Rerifying the mentioned PDF file, I remember that the solution seems to be one of the Apex installation steps on a server. Will you quie you stopped running any step in the installation in production?

Check back with the instructions that you performed when installing Apex in production. Check out these steps with the Apex installation manual, published by Oracle. Me seems to be something related to XDB user unlocking and anonimous or running some PL / SQL script to unlock Apex features.

Hugs and good luck,

Sergio Coutinho

[danielpbarros]

Then Sergio,

followed the installation instructions that exists in Glufke. All steps were successfully performed, but I can not remember having to unlock the XDB user, just the anonymous.

Att.
Daniel.

[stcoutinho]

Hmm,

then,

Is there any difference between the development environment and production? For example, the bank version, the platform, the machine only?

This problem you reports occurs with any browser? For example, did the tests with IE, Chrome, Firefox? Are the versions of these browsers are the same? Did you repeat the development and homologation tests?

I did a quick search in the OTN Forums (Oracle) .. There are several possibilities. I do not know if you performed the script that the PDF link that I passed on. If you do not feel safe to run it (because it is production) I suggest you search a little more on the OTN Forums.

Please continue posting your questions here, okay? Who knows other forists have passed the same problem?

Hugs,

Sergio Coutinho

[danielpbarros]

Hey Sergio, beleza?

I will answer the questions.

Is there any difference between the development and production environment? For example, the bank version, the platform, the machine only?

R = There is a difference in the SIM environment, such as operating system (Windows Server 2008 production and Win 7 development) but the Oracle version are the same. User machines are standardized. But the problem occurs both in development and production, so I believe it is something related to installation. When I put the SYS password, it works, but always appears the security message when the user logs on.

This problem you reports occurs with any browser? For example, did the tests with IE, Chrome, Firefox? Are the versions of these browsers are the same? Did you repeat the development and homologation tests?

R = As default in the company, Internet Explorer 8 is used on all machines. But in my notebook I tested with Mozilla and presents the same message.

I did a quick search in the OTN Forums (Oracle) .. There are several possibilities. I do not know if you performed the script that the PDF link that I passed on. If you do not feel safe to run it (because it is production) I suggest you search a little more on the OTN Forums.

R = I performed the script on the test base and the same returned error. But I realized the XDB user unlocking, continuing the same problem.
Reton the error:

Select all

ERRO na linha 1: 
ORA-31011: Falha no parse XML 
ORA-19202: Ocorreu um erro no processamento XML 
LPX-00601: Invalid token in: 
'/xdbconfig/sysconfig/protocolconfig/httpconfig/allowrepository-anonymous-access' 
ORA-06512: em "SYS.XMLTYPE", line 128 
ORA-06512: em line 7

Hugs,
Daniel.

[stcoutinho]

Hi Daniel,

I ended up appealing to Metalink and found a note that describes the problem you are facing

Troubleshooting: The XDB Login Appears When Running Apex With the 11G Enterprise PL / SQL Gateway (EPG) [ID 565952.1]

But before continuing this procedure, be sure to apply The same in a testing environment, okay?

I can not guarantee that the steps are 100%. So test in an environment that you can restore if something goes wrong.

According to the note, when the XDB login screen appears, this indicates an error in the Apex DAD configuration.

To verify that the Oracle XML Database (XDB) compiler is OK, make this queries in your database:

Select all

SELECT COMP_NAME, STATUS, VERSION FROM DBA_REGISTRY ORDER BY COMP_NAME;

If the status is as invalid, resolve the problem with the steps below:

1) Sometimes some XDB objects are invalid.
Run on the bank server:

Select all

CONN / AS SYSDBA 
DESC DBMS_LOB 
DESC UTL_FILE 
GRANT EXECUTE ON DBMS_LOB TO XDB; 
GRANT EXECUTE ON UTL_FILE TO XDB;

@?/rdbms/admin/utlrp.sql - This command recompiles the invalids / execute two or three times

2 ) Revalide XDB:

Select all

CONNECT / AS SYSDBA 
EXECUTE DBMS_REGXDB.VALIDATEXDB;

3) Check that the situation normalized:

Select all

SELECT COMP_NAME, STATUS, VERSION FROM DBA_REGISTRY ORDER BY COMP_NAME; 
SELECT OBJECT_NAME, OBJECT_TYPE, OWNER, STATUS FROM DBA_OBJECTS WHERE OWNER = 'XDB' AND STATUS != 'VALID';

4) If the problem continues , maybe you have to try to reinstall XDB:

4.1) Removing the XDB

Select all

connect / as sysdba 
shutdown immediate; 
startup 
@?/rdbms/admin/catnoqm.sql 
spool off; 

4.2) Restart the bank again:

Select all

shutdown immediate; 
startup;

]
4.3) Installing the XBD

Select all

@?/rdbms/admin/catqm.sql <XDB pwd> <XDB default tbs> <XDB temporary tbs> 
@?/rdbms/admin/utlrp.sql

/ quote]

solved the XDB problem, continue with the following steps:

1) Run (such as SYS or System) The "EPGSTAT.SQL" script located in $ORACLE_HOME/rdbms/admin

2) Check the results. The bank user for Apex DAD must be Anonymous. The authentication schema - as well as the authentication user - should also be anonymous;

3) Despite the Anonymous account with the ALTER USER ANONYMOUS ACCOUNT UNLOCK; command

4) Restart the database (Shutdown + Startup) and Listener ;

5) At this point you can take a test by accessing http://[servidor].[dominio]:8080/apex APEX login should appear without the XDB login screen;

6) Make an access test test;

I hope these steps help you solve your problem.

Hugs,

Sergio Coutinho

[danielpbarros]

Then sergio,

already in the first select to verify the valid XMLDB, did not present abnormality, since all lines are constructed as valid.

I think I'll need to recreate the XDB.

ABS,
Daniel.

[stcoutinho]

Daniel,

If XDB is valid, then you should follow these steps:

1) Run (such as SYS or System) The "EPGSTAT.SQL" script located in $ORACLE_HOME/rdbms/admin

2) Check the results. The bank user for Apex DAD must be Anonymous. The authentication schema - as well as the authentication user - should also be anonymous;

3) Despite the anonymous account with the ALTER USER ANONYMOUS ACCOUNT UNLOCK; command

4) Restart the database (Shutdown + Startup) and Listener ;

5) At this point you can take a test accessing http://[servidor].[dominio]:8080/apex APEX login should appear without the XDB login screen;

6) Take an application access test;

If after these steps, your problem continues, post here the result of the requested script In the above procedure and enter the version of your database.

Hugs,

Sergio Coutinho

[danielpbarros]

Good morning, Sérgio, how are you?

Delayed to answer due to the company's collective holidays, with this, I was able to perform the tests today successfully.
I did all verification of installation and created users. Then I performed the script that you send me by the link and restarted Bank and Listener.

Again I thank you for your help.

The script:

Select all

SET SERVEROUTPUT ON 
DECLARE 
l_configxml XMLTYPE; 
l_value VARCHAR2(5) := 'true'; -- (true/false) 
BEGIN 
l_configxml := DBMS_XDB.cfg_get(); 
IF l_configxml.existsNode('/xdbconfig/sysconfig/protocolconfig/httpconfig/allowrepository- 
anonymous-access') = 0 THEN 
-- Add missing element. 
SELECT insertChildXML 
( 
l_configxml, 
'/xdbconfig/sysconfig/protocolconfig/httpconfig', 
'allow-repository-anonymous-access', 
XMLType('<allow-repository-anonymous-access 
xmlns="http://xmlns.oracle.com/xdb/xdbconfig.xsd">' || 
l_value || 
'</allow-repository-anonymous-access>'), 
'xmlns="http://xmlns.oracle.com/xdb/xdbconfig.xsd"' 
) 
INTO l_configxml 
FROM dual; 
DBMS_OUTPUT.put_line('Element inserted.'); 
ELSE 
-- Update existing element. 
SELECT updateXML 
( 
DBMS_XDB.cfg_get(), 
'/xdbconfig/sysconfig/protocolconfig/httpconfig/allow-repository-anonymousaccess/ 
text()', 
l_value, 
'xmlns="http://xmlns.oracle.com/xdb/xdbconfig.xsd"' 
) 
INTO l_configxml 
FROM dual; 
DBMS_OUTPUT.put_line('Element updated.'); 
END IF; 
DBMS_XDB.cfg_update(l_configxml); 
DBMS_XDB.cfg_refresh; 
END; 
/