Sadly, I am not expecting much from this post. It seems there are only a few people in the oracle realm that actually understand how OAM actually works and how to integrate ADF apps with OAM.
We have a BPM environment setup with OAM for sso. There is a WLST command to set this up. What I am trying to figure out is how to set the end_url. The OAM guides talk about setting up param.logout.targeturl in the jps-config.xml on the ADF application side. There is a small sample of the setting.
<propertySets>
<propertySet name = "props.auth.url">
<property name = "login.url.BASIC" value = "http://host:port/oam_login.cgi?level=BASIC"/>
<property name = "login.url.FORM" value = "http://host:port/oam_login.cgi?level=FORM"/>
<property name = "login.url.DIGEST" value = "http://host:port/oam_login.cgi?level= DIGEST"/>
<property name = "autologin.url" value = " http://host:port/obrar.cgi"/>
<property name = "logout.url" value = "http://host:port/logout.cgi"/>
<property name = "param.login.successurl" value = "successurl"/>
<property name = "param.login.cancelurl" value = "cancelurl"/>
<property name = "param.autologin.targeturl" value = "redirectto"/>
<property name = "param.autologin.token" value = "cookie"/>
<property name = "param.logout.targeturl" value = "targeturl"/>
</propertySet>
<propertySet name="props.auth.uri">
<property name="login.url.BASIC" value="/${app.context}/adfAuthentication?level=BASIC" />
<property name="login.url.FORM" value="/${app.context}/adfAuthentication?level=FORM" />
<property name="login.url.DIGEST" value="/${app.context}/adfAuthentication?level=DIGEST" />
<property name="autologin.url" value="/obrar.cgi" />
<property name="logout.url" value="/${oamsso/logout.html" />
</propertySet>
<propertySet name = "props.auth.level">
<property name = "level.anonymous" value = "0"/>
<property name = "level.BASIC" value = "1"/>
<property name = "level.FORM" value = "2"/>
<property name = "level.DIGEST" value = "3"/>
</propertySet>
<propertySets>
<serviceProviders>
<serviceProvider name = "sso.provider"
class = "oracle.security.jps.internal.sso.SsoServiceProvider"
type = "SSO">
<description>SSO service provider</description>
</serviceProvider>
</serviceProviders>
<serviceInstances>
<serviceInstance name = "sso" provider = "sso.provider">
<propertySetRef ref = "props.auth.url"/>
<propertySetRef ref = "props.auth.level"/>
<property name = "default.auth.level" value = "2"/>
<property name = "token.type" value = "OAMSSOToken"/>
<property name = "token.provider.class" value = "oracle.security.wls.oam.providers.sso.OAMSSOServiceProviderImpl"/>
</serviceInstance>
</serviceInstances>
<jpsContexts default = "default">
<jpsContext name = "default">
<serviceInstanceRef ref = "sso"/>
</jpsContext>
</jpsContexts>
So, I do not manage BPM. I had the BPM admin send me a copy of the jps-config.xml. I do not see the propertySet called props.auth.url. It seems that this is not a default setting the that file. I an going to ask the BPM team to add it and see what happens. The dissapointing part is that this is all the information I can really find about this and oracle support has been a pain. I don't think there are many people in the org that know how all this stuff integrates.
On another note, there are a number of props.auth.uri propertySets in the jps-config.xml I was sent. It looks like you can tun the addOAMSSOProvider wlst command many times putting different parameters, therefore it appends an number, ie an index for them. That just makes it more confusing. It looks like the team has run this command a few times and now it's hard to know which propertySet is actually being used.
Is there anyone out there that has an example of setting param.logout.targeturl in this file?
If you read this far. Thank you!
Now I wait. And as stated in the beginning, I am not expecting much. It's quite sad.