title: 500 error on logging in to oiddas link: https://onemoretech.wordpress.com/2010/03/03/500-error-on-logging-in-to-oiddas/ author: lembobro description: post_id: 185 created: 2010/03/03 14:01:31 created_gmt: 2010/03/03 14:01:31 comment_status: open post_name: 500-error-on-logging-in-to-oiddas status: publish post_type: post

500 error on logging in to oiddas

Had this happen yesterday in an Oracle 10g Application Server environment. Got to the DAS Console front page (http://sso.example.com/oiddas:7777/oiddas) and hit with a “500 Internal Server Error: Contact your System Administrator”.

Being said system administrator, I did what anyone in my place would. I restarted the SSO server. NG. Then I did what I should have first, did a query on Oracle Support.

Came up with Document ID 360061.1, “Login to OIDDAS Gives 500 Internal Server Error”.

The problem was identified as due to the Site ID and Site Token encoded in osso.conf file (located at $OH/Apache/Apache/conf/osso/osso.conf and decrypted using the ssomigrate utility) not existing in the WWSSO_PAPP_CONFIGURATION_INFO$ table. The solution was to re-register mod_sso for that instance using the ssoreg.sh script.

To do this you need to source the SSO environment as your system user (e.g. “oracle”) and make sure that ORACLE_HOME and ORACLE_SID are both defined. You also should check to make sure the dcm daemon is up and running if you’re in a clustered environment (i.e., “opmnctl status”). If dcm is down, start it (”opmnctl startproc ias-component=dcm”).

Then issue this command:

$OH/sso/bin/ssoreg.sh -home_path $OH -site_name sso.example.com:443 -config_mod_osso TRUE -mod_osso_url https://sso.example.com -u oracle

Now some of the details given above may vary for your environment. For example, $OH is just an alias variable for $ORACLE_HOME, and is the install path for your 10g AS OSSO instance. The site name “sso.example.com” is whatever host and port your HTTP server for OSSO is listening on (another variation would be “hostname.domain.com:7777”. Same for the url (if you’re doing HTTPS you won’t want to list the port, but use “https://”). The “-u” flag identifies your system username. There are other parameters you might need to supply, for example if the name and/or location of osso.conf is not the default. Check the 10g AS documentation for all the variables.

Copyright 2004-2019 Phil Lembo