WWC-41653 error on Partner Application

We're trying to configure a partner application. After logging in to SSO we get the error message: "The partner application configuration is missing or expired. Please contact the administrator. (WWC-41653)"
Does anyone have any tips on where to look for this configuration problem?
Thanks in advance!

We resolved this. Our problem was a mismatch in the listener_token.

Similar Messages

ERROR : SSO Partner application could not be registered successfully

Hi,
when i run txkrun.pl to register sso my regisitration fails
perl txkrun.pl -script=SetSSOReg
You are registering ORACLE HOME, Instance with SSO and OID Servers.
Enter the host name where Oracle iAS Infrastructure database is installed ? hschbscgn20104.hclt.corp.hcl.in
Enter the LDAP Port on Oracle Internet Directory server ? 389
Enter SSL LDAP Port on Oracle Internet Directory server ? 636
Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ?
Enter the instance password that you would like to register this application instance with ?
Enter Oracle E-Business apps database user password ?
*** Log File = /data/vis/inst/apps/VIS_hschbscgn20118/logs/appl/rgf/TXK/txkSetSSOReg_Fri_Nov_19_10_05_55_2010.xml
Beginning input parameter validation for Oracle Home Instance registration.
*** ALERT: This Oracle Home Instance is already registered. Oracle Home Instance Registration will be skipped.
Input parameter validation for Oracle Home Instance registration completed.
Beginning input parameter validation for SSO registration.
Input parameter validation for SSO registration completed.
Beginning input parameter validation for OID registration.
Input parameters validation for OID registration completed.
BEGIN SSO REGISTRATION:
Beginning to register partner application.
*** ERROR : SSO Partner application could not be registered successfully.
End of /data/vis/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered
Below is my Log file:
BEGIN SSO REGISTRATION:</message>
</record>
<record>
<date>2010-11-18T23:31:11</date>
<millis>1290103271727</millis>
<sequence>79</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.TXKSTDIO</class>
<method>info</method>
<thread>10</thread>
<message>Beginning to register partner application.</message>
</record>
<record>
<date>2010-11-18T23:31:11</date>
<millis>1290103271728</millis>
<sequence>80</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.config.Instance</class>
<method>updateIasProperties</method>
<thread>10</thread>
<message>updating ias.properties file by retrieving data from DB</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272017</millis>
<sequence>81</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.config.Instance</class>
<method>updateIasProperties</method>
<thread>10</thread>
<message>Retrieved Preferences: {IASname=VIS.hclt.corp.hcl.in, InfrastructureDBCommonName=ORAAS.HCLT.CORP.HCL.IN, InfrastructureUse=true, OIDhost=hschbscgn20104.hclt.corp.hcl.in, SSLOnly=false, OIDsslport=636, IASpassword=05a78096c85355eed5aa08f04546377eb5e16520f2237467b7, OIDport=389}</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272018</millis>
<sequence>82</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.config.Instance</class>
<method>updateIasProperties</method>
<thread>10</thread>
<message>ias.properties is latest. No need to update.</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272019</millis>
<sequence>83</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>ssoReg</method>
<thread>10</thread>
<message>Processing APPS_FRAMEWORK_AGENT: https://hschbscgn20118.hclt.corp.hcl.in:443</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272019</millis>
<sequence>84</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>removePortsFromAgent</method>
<thread>10</thread>
<message>Agent:https://hschbscgn20118.hclt.corp.hcl.in:443
After removing default ports Agent:https://hschbscgn20118.hclt.corp.hcl.in</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272053</millis>
<sequence>85</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.DBUtil</class>
<method>getAgentConfFileId</method>
<thread>10</thread>
<message>Executing: SELECT PREFERENCE_NAME FROM FND_USER_PREFERENCES WHERE PREFERENCE_NAME LIKE 'TXK_SSO_FILE_ID_%' AND PREFERENCE_VALUE = 'https://hschbscgn20118.hclt.corp.hcl.in' AND MODULE_NAME = 'LDAP_SYNCH' AND USER_NAME = '#INTERNAL' </message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272054</millis>
<sequence>86</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.DBUtil</class>
<method>getAgentConfFileId</method>
<thread>10</thread>
<message>file id NOT found</message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272055</millis>
<sequence>87</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>updateReqArgs</method>
<thread>10</thread>
<message>Updated Required Arguments Map: -site_name=https://hschbscgn20118.hclt.corp.hcl.in -appspass=******* -config_mod_osso=true -logout_url=https://hschbscgn20118.hclt.corp.hcl.in/OA_HTML/AppsLogoutSSO -home_url=https://hschbscgn20118.hclt.corp.hcl.in -config_file=/data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3/Apache/Apache/conf/osso/VIS_hschbscgn20118_osso.conf -update_mode=CREATE -success_url=https://hschbscgn20118.hclt.corp.hcl.in/osso_login_success -cancel_url=https://hschbscgn20118.hclt.corp.hcl.in </message>
</record>
<record>
<date>2010-11-18T23:31:12</date>
<millis>1290103272056</millis>
<sequence>88</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>ssoReg</method>
<thread>10</thread>
<message>Commmand is : sh /data/vis/apps/tech_st/10.1.3/sso/bin/ssoreg.sh -site_name https://hschbscgn20118.hclt.corp.hcl.in -config_mod_osso true -logout_url https://hschbscgn20118.hclt.corp.hcl.in/OA_HTML/AppsLogoutSSO -home_url https://hschbscgn20118.hclt.corp.hcl.in -config_file /data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3/Apache/Apache/conf/osso/VIS_hschbscgn20118_osso.conf -update_mode CREATE -success_url https://hschbscgn20118.hclt.corp.hcl.in/osso_login_success -cancel_url https://hschbscgn20118.hclt.corp.hcl.in</message>
</record>
<record>
<date>2010-11-18T23:31:14</date>
<millis>1290103274625</millis>
<sequence>89</sequence>
<logger>txkSetSSOReg</logger>
<level>INFO</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>ssoReg</method>
<thread>10</thread>
<message>Return Code is : 1</message>
</record>
<record>
<date>2010-11-18T23:31:14</date>
<millis>1290103274625</millis>
<sequence>90</sequence>
<logger>txkSetSSOReg</logger>
<level>SEVERE</level>
<class>oracle.apps.fnd.txk.ias.sso.Instance</class>
<method>ssoReg</method>
<thread>10</thread>
<message>CLASSPATH=/data/vis/apps/tech_st/10.1.3/jdbc/lib/ojdbc14.jar:/data/vis/apps/tech_st/10.1.3/jlib/repository.jar:/data/vis/apps/tech_st/10.1.3/sso/lib/ossoca.jar:/data/vis/apps/tech_st/10.1.3/sso/lib/ossoreg.jar:/data/vis/apps/tech_st/10.1.3/lib/xmlparserv2.jar:/data/vis/apps/tech_st/10.1.3/jdbc/lib/classes12.jar:/data/vis/apps/tech_st/10.1.3/jdbc/lib/nls_charset12.jar:/data/vis/apps/tech_st/10.1.3/jlib/jndi.jar:/data/vis/apps/tech_st/10.1.3/jlib/ojmisc.jar:/data/vis/apps/tech_st/10.1.3/j2ee/home/jazn.jar:/data/vis/apps/tech_st/10.1.3/j2ee/home/jaas.jar:/data/vis/apps/tech_st/10.1.3/jdk/lib/rt.jar:/data/vis/apps/tech_st/10.1.3/jdk/lib/i18n.jar:/data/vis/apps/apps_st/comn/java/classes/oracle/apps/fnd/jar/fndoid.jar:/data/vis/apps/tech_st/10.1.3/jdbc/lib/ojdbc14.jar:/data/vis/apps/tech_st/10.1.3/jdbc/lib/orai18n.jar:/data/vis/apps/tech_st/10.1.3/jlib/repository.jar:/data/vis/apps/tech_st/10.1.3/jlib/infratool.jar:/data/vis/apps/apps_st/comn/java/classes:/data/vis/apps/tech_st/10.1.3/sysman/webapps/emd/WEB-INF/lib/emd.jar:/data/vis/apps/tech_st/10.1.3/dcm/lib/dcm.jar:/data/vis/apps/tech_st/10.1.3/sysman/j2ee/lib/portalSMI.jar:/data/vis/apps/tech_st/10.1.3/jlib/emConfigInstall.jar:/data/vis/apps/tech_st/10.1.3/lib/dms.jar:/data/vis/apps/tech_st/10.1.3/opmn/lib/ons.jar:/data/vis/apps/tech_st/10.1.3/j2ee/home/oc4j.jar
Parameters passed to SSO registration tool :
param0:-oracle_home_path param1:/data/vis/apps/tech_st/10.1.3 param2:-site_name param3:https://hschbscgn20118.hclt.corp.hcl.in param4:-config_mod_osso param5:true param6:-logout_url param7:https://hschbscgn20118.hclt.corp.hcl.in/OA_HTML/AppsLogoutSSO param8:-home_url param9:https://hschbscgn20118.hclt.corp.hcl.in param10:-config_file param11:/data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3/Apache/Apache/conf/osso/VIS_hschbscgn20118_osso.conf param12:-update_mode param13:CREATE param14:-success_url param15:https://hschbscgn20118.hclt.corp.hcl.in/osso_login_success param16:-cancel_url param17:https://hschbscgn20118.hclt.corp.hcl.in
-DinstallType=
-DORACLE_CONFIG_HOME=/data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3
-DoldOracleHome=
-DoldOHSUser=root
Check /data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3/sso/log/ssoreg.log for details of this registration
SSO registration tool failed. Please check the log file /data/vis/inst/apps/VIS_hschbscgn20118/ora/10.1.3/sso/log/ssoreg.log, correct the problem and re-run the tool.
.end std out.
.end err out.
</message>
</record>
<record>
<date>2010-11-18T23:31:14</date>
<millis>1290103274626</millis>
<sequence>91</sequence>
<logger>txkSetSSOReg</logger>
<level>SEVERE</level>
<class>oracle.apps.fnd.txk.ias.TXKSTDIO</class>
<method>exception</method>
<thread>10</thread>
<message>oracle.apps.fnd.txk.ias.SsoOidException: SSO Partner application could not be registered successfully.
at oracle.apps.fnd.txk.ias.sso.Instance.ssoReg(Instance.java:470)
at oracle.apps.fnd.txk.ias.sso.Instance.registerPartnerApp(Instance.java:690)
at oracle.apps.fnd.txk.ias.Instance.main(Instance.java:88)
</message>
</record>
</log>
can anyone tell me what is the problem

Hi
Please refer doc and do the following steps.
1. Take a copy of the $IAS_ORACLE_HOME/Apache/Apache/bin/iasobf file
2. Change the ORACLE_HOME=to the correct IAS_ORACLE_HOME
3. Re-run the SSO registration by following the three step process
Regards,
Krishna

OID connection error for partner application

Hello All
I have registered a partner application which run from Oracle application server OC4J and when i login via URL, I get following error below, any suggestions?. All parameters are correctly specified.
AJPRequestHandler-ApplicationServerThread-458 Communication Exception received. Cleaning up the stale
connection
oracle.ldap.util.CommunicationErrorException: Unable to establish connection to directory. Please verify the input parameters: host, port,
dn &' password connection closed
at oracle.ldap.util.Subscriber.getUser_NICKNAME(Subscriber.java:1214)
at oracle.ldap.util.Subscriber.getUser(Subscriber.java:913)
at oracle.ldap.util.Subscriber.getUser(Subscriber.java:860)
at oracle.security.sso.server.ldap.OIDUserRepository.getUserProperties(OIDUserRepository.java:495)
at oracle.security.sso.server.auth.SSOServerAuth.authenticate(SSOServerAuth.java:485)
at oracle.security.sso.server.ui.SSOLoginServlet.processSSOPartnerRequest(SSOLoginServlet.java:1058)
at oracle.security.sso.server.ui.SSOLoginServlet.doPost(SSOLoginServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:835)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:341)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:816)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:231)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:136)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Thanks
Amit

Hi Amit,
I am also facing the same issue. Could you please share the work around you around to get rid of this issue?
Mahendra.

LOGIN ERROR: "The partner application configuration is missing or expired."

"portal" login pswd had expired and I changed it a) via OEM under "configure schema" section anb b) under HTTP->PL/SQL Properties section. I also went to OIDADMIN and changed the "portal" user pswd to the same schema pswd used above. However, now when logging in with the "portal" ID I'm getting the error above. Does anyone have any idea what this is and what I should do? THANKS!

hi
have you ran any scripts or did you change your system dates after the installation.
Regards
Deepak

Wwc- 41653 The partner application configuration is missing or expired.

We have the following scenerio.
Application server 9iR1, apache server, login server, portal3.0.9.8.4 on 9iR2 database on host A. There is another database in 9iR2 where portal3.0.9.8.4 installed on host B. I want to use this database for another website configuring apache on host A as virtual host. I want to use same login server on host A.
The website on host A is working fine while the website on host B does not allow me to log into the login server.
I have run ssodatan script for associating portal schema on host B. I have created partner application on host A portal for accessing portal on host B and run ssodatax script for associating partner application.
when I try to log into the another web site created for host B, I get portal welcome page. when I click on login, I get sso page but i am unable to log into it, getting error The partner application configuration is missing or expired. Please contact the administrator. (WWC-41653)
How to resolve this?

Were you able to resolve the issue???
Can you pls try Rerunning ssodatan/x with the correct data. The ssodatan script is located in the directory ORACLE_HOME/portal30/admin/plsql/ssodatan.
Refer following link for more info on SSODATAN , SSODATAX and DIAGNOSTICS scripts in Portal 3.0.x:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=136138.1

Partner application configuration is missing error on SSO login page

We have APEX 3.1.2 setup as a partner application and an application within APEX setup to use SSO for authentication. Following a link to the APEX application redirects to the Single Sign-On page, as it should, but it also shows "Error: The partner application configuration is missing or expired." I type in my password and username, click the Login button, and (if I entered my username and password correctly, of course!) then the APEX application is shown. So, I cannot figure out why we're getting the no_papp_err error and I have not found any solutions to that issue on Metalink or anywhere else on the Internet. Any ideas? I'm concerned that we have a misconfiguration somewhere that is causing this error and will affect any other partner application we setup in the future.
We're on Oracle Portal 10.1.4, SSO 10.1.2, and SSL is setup on both infra and mid tiers.

Did you try checking the partner application entries on the SSO-login server page?
please login as orcladmin or some other user with membership in, i beleive, iasadmins group. verify that for this partner application, what you see here corresponds to the application URL. it looks like your login page call may have issues. so check for login url too.
also check the ORASSO.WWSSO_LS_CONFIGURATION_INFO$ for entries corresponding to Apex application.

Error: Partner application configuration is missing ... on SSO login page

We have APEX 3.1.2 setup as a partner application and an application within APEX setup to use SSO for authentication. Going to the APEX application redirects to the Single Sign-On page, as it should, but it also shows "Error: The partner application configuration is missing or expired." I type in my password and username, click the Login button, and (if I entered my username and password correctly), it redirects me to the APEX application just like it should. So, I cannot figure out why we're getting the no_papp_err error and I have not found any solutions to that issue on metalink or anywhere else on the Internet. Any ideas?
We're on Oracle Portal 10.1.4, SSO 10.1.2, and SSL is setup for both.
+Closing this topic and opening it in [Oracle Application Server - General|http://forums.oracle.com/forums/thread.jspa?threadID=832022&tstart=0|New Topic]+
Edited by: oportalist on Nov 28, 2008 10:24 AM

Did you try checking the partner application entries on the SSO-login server page?
please login as orcladmin or some other user with membership in, i beleive, iasadmins group. verify that for this partner application, what you see here corresponds to the application URL. it looks like your login page call may have issues. so check for login url too.
also check the ORASSO.WWSSO_LS_CONFIGURATION_INFO$ for entries corresponding to Apex application.

Error on registering Flights of Fancy application(Partner Application, JPDK) provide

Hi
When i try to add a provider for Flights of Fancy application i am getting this error
An error occurred when attempting to call the providers register function. (WWC-43134)
The following error occurred during the call to Web provider: Unable to initialize new provider instance: oracle.portal.provider.v1.ProviderException: Portlet PartnerFlightPortlet: Required Renderer not set. (WWC-43147)
i am able to access the URL (http://myhost/servlet/flightsprov) without any problem and is displaying the following information
Congratulations! You have successfully reached your Provider's Test Page.
Checking for components:
Oracle XML parser: detected
Oracle JSP: detected
Recognizing initArgs: Usual initArgs are provider_root and sessiontimeout.
dbhost: myhost
partnerAppCookieDomain: mydomain.com.qa
dbsid: mysid
onCancelUrl: http://myhost
partnerAppCookieDesc: SSO application cookie
partnerAppCookieScope: /
dbSchema: mypartner
requestedUrl: http://myhost/servlet/flights
provider_root: D:\port\partner
dbport: 1521
dbPassword: mypartner1
partnerAppCookieName: SSO_PAPP_SERVLET_ID
sessiontimeout: 1800000
listenerToken: myhost:80
ANd i make sure several times that i am using the same URL for Portal registration page.
In the jserv.log file i am getting the following information
[08/04/2001 13:08:24:642 GMT+03:00] flightsprov/javax.servlet.ServletException: Unable to initialize new provider instance: oracle.portal.provider.v1.ProviderException: Portlet PartnerFlightPortlet: Required Renderer not set.
at oracle.portal.provider.v1.http.HttpProvider.getProvider(HttpProvider.java:339)
at oracle.portal.provider.v1.http.HttpProvider.service(HttpProvider.java:246)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java, Compiled Code)
at org.apache.jserv.JServConnection.run(JServConnection.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
Can anybody help me in solving this problem
thanks in advance
Abdulla
null

You're not missing anything - it sounds like it's working perfectly.
If a provider is affiliated with a partner application, the provider is automatically authenticated when you authenticate to the portal - because it is also a partner application. You only need to authenticate yourself once.
Now, when you go to the partner application, the application session cookie that was created by the provider is passed to the partner application & so you are not challenged.
Now, if you close your browser and access the partner application first, the login server will challenge you. When you subsequently go to the portal, you will not be challenged - the portal contacts the login server behind the scenes, determines you have already authenticated yourself and proceeds as if you had logged in.
When you visit the partner provider portlet, it will detect the cookie created by the partner application and use that to tie into the same session.
This is the whole point of single sign on.

Error when trying to configure Lync to be a partner application for Exchange Server 2013

When I attempt to run the Configure-EnterprisePartnerApplication.ps1 script I get the following error:
The address 'LyncEnterprise-ApplicationAccount@*.domain.com' is invalid:
"LyncEnterprise-ApplicationAccount@*.domain.com" isn't a valid SMTP address. The domain name can't contain spaces and it has to have a prefix and a suffix, such as example.com.
The error continues with some more things, but what I can't understand is why it is adding a *. after the @ when it is trying to create the account.
Any help would be appreciated, thanks!

Hi ADrake04,
I found that the script was configured as below:
$acceptedDomains = Get-AcceptedDomain;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains[0].Name;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
WriteInformation ("Created User <$($user.Identity)> for Partner Application.");
return $user;
Please note the variable “$acceptedDomain”,
this is a very important point.
(Note: The acceptdomain is used in Exchange, and can be created in Exchange EAC )
Now what you need to do is to run the following command in Exchange Powershell and see the result.
$acceptedDomains
= Get-AcceptedDomain
$acceptedDomains[0].Name
If you see the result “*.Domain.com”, then you should check your Exchange Configuration.
Best regards,
Eric

Error running ssodatax script for partner applications

I am running the ssodatax script after creating a partner
application using the user interface in the portal. I get the following
error after the script starts running:
SP2-0310: unable to open file "sso/ssoseedp.sql"
Any thoughts will be appreciated.
Thanks,
Suzanne

It appears that ssodatax in your environment is unable to find the script ssoseedp.sql. This script should be available in plsql/sso directory under the ORACLE_HOME. Please find the script ssodatax and look for the sso subdirectory within the directory that contains ssodatax. If you find ssoseedp.sql in sso, then you can try running ssodatax from the directory that contains it.

The partner application configuration is missing

Trying to login to portal with portal30 leads to
'The partner application configuration is missing or expired. Please contact the administrator. (WWC-41653)'
Please advise
db 8.1.7
portal 3.0.9
apserver 1.0.2.1
Thank you
Anatoliy Smirnov

Were you able to resolve the issue???
Can you pls try Rerunning ssodatan/x with the correct data. The ssodatan script is located in the directory ORACLE_HOME/portal30/admin/plsql/ssodatan.
Refer following link for more info on SSODATAN , SSODATAX and DIAGNOSTICS scripts in Portal 3.0.x:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=136138.1

Partner Application Registration

When using the Administer Partner Applications page, it appears the application is not being registered completely. The information does not appear in the WWSEC_ENABLER_CONFIG_INFO$ table, as has been suggested in prior posts (everything is fine in WWSSO_PAPP_CONFIGURATION_INFO$).
I am attempting to deploy the SSO SDK demo PL/SQL application, which works fine when logged into Portal. However, when not logged into Portal, I receive the following errors:
"Error in application: missing application registration information
Please register this application as described in installation guide"
This error is driven by the PL/SQL exception:
"wwsec_sso_enabler_private.enabler_config_not_found"
What am I missing? I have created several Partner applications, and none of them appear in the WWSEC_ENABLER_CONFIG_INFO$ table. I have sucessfully loaded the SSOHash into my partner schemas.
Environment:
Win2000
Portal 3.0.7
Thanks in advance...
Dean

Paul,
Thanks for the info; however, I'm still unable to get the SSO SDK sample, or any partner app, to work.
I have read the docs, what little there is, and followed the steps closely. Everything executes ok.
I have several questions:
1. When executing the REGAPP.SQL script that comes with the SDK, it indicates to login as the partner schema. I have noticed when running this script, the entry is stored in the partner schema table WWSEC_ENABLER_CONFIG_INFO$, not the one owned by Portal. Is this correct?
2. My partner app is really a PL/SQL Server Page (PSP) application which uses the same server as Portal. When entering the Listener Token name, I have been using the same server name as Portal. Is this a problem? What is this token used for? Must it be unique for each partner application?
3. In your response you mentioned changes to the REGAPP script. I found no mention of any changes in the docs with SSO SDK. Am I missing something?
Finally, is there any better documentation for the SDK and/or partner application configuration. The readme and install files do not, in my opinion, pass as documentation.
Thanks...
Dean

Partner application and web clipping.

Hi All,
I am trying to add an external application (say my.yahoo.com) to a webclipping and its throwing the below error in the application log.
WC-517 : SSL handshake failed with the url ...
I have checked the file ca-bundle.crt and the certificates are in place. Does anybody know how to go about debugging this problem as I am quite new to portals and at my wits end to solve it.
Also I would be greatful if anybody can suggest me the steps on adding an Apex application configured as partner application with SSO authentication to a web clipping.There seems to be little or no-documentation at all in this regard(as far as my search goes).
Thanks in advance
-Venkat

I finally got it working by VERY CAREFULLY reading the instructions in the install.txt document in the SSO SDK package. You have to set up the partner application with a new schema in the login server database, and run the regapp.sql script AFTER editing it to insert data from the Login Server Partner Application admin screen. After you register the partner app in Portal, it gives you some info (site token, listener token, encryption key, etc). You have to MANUALLY copy these and paste them into the regapp.sql script, then run the script in the partner app schema. Make sure you don't confuse capital I with numeral 1 (like I did, since Oracle so nicely uses a non-serif font where you can not tell the difference).
Also make sure you copy the exact values for these parameters into your code when you use the SSOEnabler class. The listener token was very confusing since different documents appear to disagree on whether it should include the partner app name or not. It does require the partner app name:
app-name:hostname:port
hostname and port are for the web server that is handling http requests for the login server (usually your main portal web server).
John H.

SSO Partner Application not working

Hi,
I have OBIEE running on a different box. I need to enable SSO for OBIEE. I deployed the analytics.war file in the home oc4j container of Oracle Portal and manually registered it as a Partner Application, made following changes in mod_osso.conf inside ORACLE_PORTAL_HOME/Apache/Apache/conf and restarted the apache server. But when I access the application it does shows me the SSO login page but after entering the credentials it throws internal server error. I checked the log files but don't see any errors in there so wondering what could be wrong.
Here is what I have added in the mod_osso.conf
<Location /analytics>
Header unset Pragma
OssoSendCacheHeaders off
AuthType Basic
require valid-user
</Location>Any help is appreciated.
Thanks

please check your $ORACLE_HOME/sso/log/ssoreg.err and $ORACLE_HOME/sso/log/ssoreg.log and see if you have errors in your sso-registration.
thanks!
AMN

Apex application registered with sso as partner application

We have 1 apex app registered with sso and working properly.
I just registered a new apex application with sso. when i authenticate through sso, it directs me to the originally registered application.
I went in through the portal administrator app and verified my settings all pointed to the new application. I verified that my dad is set up correctly.
Any ideas?
APEX 2.0

i did register and obtain the keys through portal admin.
to ensure i used the proper keys (i guess there is a possibility i used the keys from db1 registration) i re-ran regapp with the right keys but recieved the following output:
SQL> @regapp
Partner Application Configuration
Enter value for listener_token: HTML_DB:050iasphttp.xxx.na.xxx.com:7777
Enter value for site_id: EFBE3E14
Enter value for site_token: MSMXURH1EFBE3E14
Enter value for login_url: https://050iaspdb.xxx.na.xxx.com:4443/pls/orasso/orasso.wwsso_app_admin.ls_login
Enter value for encryption_key: 2EBDD126A3A40606
Enter value for ip_check: N
ERROR: Error in registration. Please try again
User-Defined Exception
Registration successful.
Listener token: HTML_DB:050iasphttp.xxx.na.xxx.com:7777
Site id : EFBE3E14
Site token : MSMXURH1EFBE3E14
Encryption key: 2EBDD126A3A40606
Login URL :
https://050iaspdb.xxx.na.xxx.com:4443/pls/orasso/orasso.wwsso_app_admi
n.ls_login
Logout URL :
https://050iaspdb.xxx.na.xxx.com:4443/pls/orasso/orasso.wwsso_app_admi
n.ls_logout
IP check : N
PL/SQL procedure successfully completed.
Commit complete.
No errors.
SQL>
...in spite of the error, i aske the app developer to try and use sso for db2. he now recieves:
User-Defined Exception
Error Error in wwv_flow_custom_auth_sso.process_success:l_sso_user_name:l_sess_id:: Please contact administrator.
OK
any ideas?

WWC-41653 error on Partner Application

Similar Messages

Maybe you are looking for