Error in OID ldap integration

Question

I'm trying to integrate Portal and OID authentication.
I followed all the documentation in conf_ldap.pdf but I get the error:Unexpected errors (WWC-41400).
Both the tnsping exproc_connection_data
and lsnrctl status give the right result as stated in the document.
So I've tryed to launch from portal30_sso user this command:
select WWSSO_AUTH_EXTERNAL.authenticate_user('portal30','portal30') from dual
and I get the error:
ORA-28576: lost RPC connection to external procedure agent
ORA-06512: at "PORTAL30_SSO.WWSSO_AUTH_EXTERNAL", line 281
ORA-06512: at line 1
Both tnsnames.ora and lisner.ora seems to be configures fine.
I'm using OID coming from Oracle 8.1.7.0 and OiAS 1.0.2.1 for NT on a win 2000 sp1,
Where is the problem?
Thank's in advance
Mauro
null

Answer 1

Here are some things to check:
I beleive that some of the newer versions of Portal have a user
called "portal309_sso" instead of "portal30_sso". My examples
below use portal30_sso". Use whatever user is appropriate for
your version of Portal.
If you have not yet installed OID (Oracle's LDAP server) none of
this will work. Make sure OID is installed and running. OID can
be installed in the same database that Portal uses.
All of the following sql command steps must be executed as
portal30_sso schema user, NOT portal30.
Examples for NT:
Copy the appropriate library file (ssoxldap.dll) used for the
LDAP API callouts from the $PORTAL_HOME/portal30/admin/plsql/sso
directory of the product installation into the appropriate place
on the Login Server machine:
Examples for NT copy:
F:\>copy \PORTAL_HOME\portal30\admin\plsql\sso\ssoxldap.dll
ORACLE_HOME\bin
F:\>sqlplus portal30_sso/portal30_sso create or replace library
auth_ext as F:\Oracle\Ora8db\bin\ssoxldap.dll';
Notice that you must type a forward slash on a line by itself
after you execute the command.
Make sure that your network connectivity is working.
Make sure you have at least 1 service handler for PLSExtProc:
Example:
F:\>set ORACLE_HOME=F:\Oracle\Ora8db
F:\>lsnrctl status
PLSExtProc has 1 service handler(s)
Make sure you can tnsping extproc_connection_data.
Example:
F:\>tnsping extproc_connection_data
Attempting to contact (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0))
OK (80 msec)
F:\>
If either of these two network connectivity checks fail nothing
else will work.
Next make sure you enter the correct information for the
ssoldap.sql script. One small typing error will cause the problem
you had. In the example below there are a couple of common
mistakes people make. Make sure you type the full Search base.
The value for the search base should be "cn=Login Server
(portal30_sso)". Don't forget the cn= and be sure to put in the
spaces and capitol letters where you see them. In the "Bind DN"
make sure you dont forget to put in the "cn=" in front of the
"orcladmin".
Example:
sqlplus portal30_sso/portal30_sso
@\oracle\isuites9i\portal30\admin\plsql\sso\ssoldap
Host: 144.25.95.92
Port: 389
Search Base: cn=Login Server (portal30_sso)
Unique Attribute: cn
Bind DN: cn=orcladmin
Bind Password: welcome
Note: If you have already changed the password for cn=orcladmin
in the OID LDAP server you must use that password instead of
"welcome" for the "Bind Password:".
Creating the users.ldif file for migrating existing users in the
portal30 database schema.
sqlplus portal30_sso/portal30_sso
@f:\oracle\isuites9i\portal30\admin\plsql\sso\ssoldif
Generating 'users.ldif' file for existing Portal users.
Enter the desired file location.
F:\oracle\admin\oiddb2\udump
NOTE: The file location must be specified in the appropriate
parameter in the init.ora file.
Example (you should see a line like this in the init.ora file):
UTL_FILE_DIR = F:\Oracle\admin\oid2111\udump
This line specifies where to dump data the you want to migrate.
If this line was not present in the init.ora file before you
started your database you will have to restart the database for
this step to succeed.
Using the file that was created in the last step (users.ldif),
add the entries to the LDAP directory. This example uses Oracle
Internet Directory's ldapadd command line utility:
Note. The following command is one long line. If you have already
done this next step before you may want to go into OID and delete
the existing data that is already in OID. Use the ODM (Oracle
Directory Manager) tool to do this. Under "Entry management" make
sure you delete any entries that you may have already created. If
the directory entries already exist you will get an error when
you run the next command indicating that the entries already
exist. Because any previous entries you may have created may not
be good those entries should be deleted.
ldapadd -h 144.25.95.92 -p 389 D cn=orcladmin -w welcome f
f:\oracle\admin\oiddb2\udump\users.ldif
Once these users are successfully added, you are ready to log
into the Portal through the Login Server, authenticating against
this LDAP directory.
Make sure you login as a valid user that is under the "cn=Login
Server (portal30_sso)" directory of your LDAP server.
Example:
Open your browser and go to the URL:
http://ip_or_hostname:80/pls/portal30
Click on the Login link
Login as portal30_sso/portal30_sso
Note: Assuming portal30_sso is a valid user in the LDAP server. I
beleive that some of the newer versions of Portal have a user
called "portal309_sso" instead of "portal30_sso".
Hope this helps.
Jay