Bug 794289 (JBEPP-1341)

Summary: Upgrade SPNEGO integration documentation
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: mposolda
Component: DocumentationAssignee: Scott Mumford <smumford>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.ER05CC: epp-bugs, jmorgan, mposolda, smumford, theute
Target Milestone: ---   
Target Release: 5.2.0.Docs.GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1341
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-28 02:16:08 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mposolda 2011-11-03 21:52:39 UTC
project_key: JBEPP

SPNEGO configuration has been changed as now it supports fallback to FORM authentication. See JBEPP-1099 . After upgrade of GateIn documentation ( GTNPORTAL-2257 ) we also need to do same changes in EPP docs.

Comment 1 mposolda 2011-11-03 21:53:04 UTC
Link: Added: This issue relates to JBEPP-1099


Comment 2 mposolda 2011-11-03 21:53:04 UTC
Link: Added: This issue relates to GTNPORTAL-2257


Comment 3 mposolda 2011-11-09 21:35:01 UTC
Scott,
I've updated GateIn reference guide with latest changes needed for SPNEGO authentication. You can see the diff of changes here https://source.jboss.org/viewrep/GateIn/portal/trunk/docs/reference-guide/en-US/modules/AuthenticationAndIdentity/SSO.xml?r1=8015&r2=8017

There is bigger amount of changes because there is support for new feature required by customers (SPNEGO support with fallback to FORM authentication). There is an exception that you don't need to apply the step with upgrading JBoss Negotiation library (lines 1320-1326 from diff link above) because EPP already have correct version of Negotiation 2.0.4.GA. So this step is required only for GateIn but it's not required for EPP.

Let me know if you have questions.

Comment 4 Jared MORGAN 2011-11-09 21:47:32 UTC
Hi Marek

Hmm, I'm wondering if the SPNEGO info could be incorporated into the JBoss Enterprise Application Platform Negotiation User Guide. Eva Kopalova has been working on this for EAP 5.1.2.

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-single/Negotiation_User_Guide/index.html

It makes sense to me to remove docs duplication between projects if we can use a base set of documentation relevant to multiple JBoss Middleware platforms.

An example of this is the HTTP Connectors Guide, which is compatible with EAP and EWS.

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-single/HTTP_Connectors_Load_Balancing_Guide/index.html

Comment 5 Thomas Heute 2011-11-09 22:03:05 UTC
This part is about using SPNEGO in the context of EPP, so it wouldn't apply to EAP guide

Comment 6 Scott Mumford 2011-11-10 01:21:52 UTC
Thanks Marek,

I've rolled the changes in. 
Please review and confirm once the next version of the Reference Guide is staged (will ping Portal list).

Comment 7 mposolda 2011-11-10 08:49:19 UTC
Jared: IMO it can be useful to add a link to Negotiation guide into our EPP guide. In EPP guide, we have especially informations, which are useful only for EPP and we have instructions how to make it work with EPP. But Negotiation guide contains more general informations and more troubleshooting tips and other instructions (for example instructions for Active Directory setup), so it makes sense to add link to this guide in our doc. Think is that I am not seeing link to Negotiation guide here http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/index.html, seems that this guide is something new. So it seems that link can be added later (after Negotiation guide will be uploaded to docs.redhat.com).

Scott: Thanks

Comment 10 Jared MORGAN 2011-11-11 03:13:51 UTC
Release Notes Docs Status: Added: Not Required


Comment 11 Scott Mumford 2011-11-28 02:16:08 UTC
Resolving as the original request has been actioned.

Other considerations can be dealt with elsewhere.