Link: Added: This issue depends SOA-731

Hi Darrin,

Could you please help me to add following section into the '1.8 Configuring OpenSSO in SOA-P' of  'JBoss_Enterprise_Platform_Administration_Guide' book.

============================

1.8.2 Install and configure Opensso in SOA-P

Due to an opensso.war deployment issue (https://jira.jboss.org/jira/browse/SOA-731), we have provided a workaround to fix it. 
We are testing against OpenSSOv1 Build 4.5 (http://download.java.net/general/opensso/stable/openssov1-build4.5/)

  1. Go to $SOA-P/jboss-as/samples/quickstarts/opensso/opensso-ear, run 'ant'.
  2. Copy the opensso-1.0.ear from $opensso-ear/build to $SOA-P/jboss-as/server/$config(such as default)/deploy
  3. Start the soa-p from $soa-p/jboss-as/bin/run.sh
  4. Open http://localhost:8080/opensso in a browser.
  5. Click on "Create Default Configuration". This causes OpenSSO to
     configure itself.
  6. Enter 'adminpass' for the "Default User[amAdmin]" and 'ldappass'
     for "Default Agent [amldapuser]"
  7. Visit http://localhost:8080/opensso again. Log in
     using the proper credentials. User Name is amAdmin and Password
     is the password you chose to go with amAdmin.

  More information about opensso, please visit its website at: http://opensso.dev.java.net

=============================

Hi Darrin,

Could you please help me to include the above message in the 'Administration_Guide' book?

Thanks
Jeff

Parent: Added: SOA-1076

Parent: Removed: SOA-1076 

Link: Added: This issue is a dependency of SOA-1076

I assume this section should replace the installation on Tomcat section ?

I suggest that we add another section next to Tomcat one, instead of replacing the Tomcat section. 

Thoughts?

But this method is preferred, ie installing in SOA? 

Hmm... I would not say it is preferred, since the solution that we provide this time is still a workaround, not perfect one(The perfect one would be fixed in the opensso itself). But we might add this one before the Tomcat one.
Need MarkL's call here. ;-)

@Mark 
Thoughts?

Thanks
Jeff

emailed soa-pm-list to clarify

replaced tomcat instructions from the previous version with this new content

quick question.
in login-config.xml should it be:
<module-option name="amPropertiesFile">/props/AMConfig.properties</module-option>
or 
<module-option name="amPropertiesFile">props/AMConfig.properties</module-option>

I have no idea but the leading / seemed odd to me.

Link: Added: This issue is a dependency of SOA-1169

Hi Darrin,

Make it consistent with others, use the:

<module-option name="amPropertiesFile">props/AMConfig.properties</module-option> 

Without the leading /.

Thanks
Jeff

updated

Release Note:
SOA-731
The OpenSSO deployment instructions in the Configuration chapter of the Administration Guide have been updated.

as per email exchange on 26/27th of February, reverting back to Tomcat installation instructions

verifying tomcat installation: the instructions say build 4.5 but it seems to be no longer available on the site.

Can we give people more specific instructions on the correct version's location ?

Hi Darrin,

The specific location is: http://download.java.net/general/opensso/stable/openssov1-build4.5/

Thanks
Jeff

content updated in guide with tomcat instructions again

Just to confirm - we are going to follow the model of the opensso quickstart readme file and document BOTH the tomcat install and the opensso.ear install into the SOA-P server?

As of today - Mar 16 14:00 UTC, the admin guide here: https://svn.corp.jboss.com/repos/soa/branches/4.3/build-tools/docs/esb/   only lists the tomcat install.

Darrin - are the doc changes available for review? Thx.

I reverted back to the Tomcat instructions for the Administration Guide as the email discussion of the EAR install stated that it was unsupported.  I have included reference to the EAR install additions to the quickstart in the release notes.

Note added to section 9.1 page 8 in the release notes

The confusion here was over the tomcat install approach being recommended and the .EAR install into SOA-P being provided as a workaround. The quickstart readme file has also been updated to be in synch.