Hide Forgot
Date of First Response: 2010-06-02 21:17:07 project_key: SOA EAP 5.0.1: <role-name>JBossAdmin</role-name> SOA-P 5.0.2 CR1: <role-name>user</role-name> Just FYI the xml formating of web.xml and jboss-web.xml ins SOA-P looks quite ugly.
Attached the 5.0.1 and 5.0.2 CR1 files - what happened to the file?
Attachment: Added: 501_web.xml Attachment: Added: 502_web.xml
The change is a side-affect of the changes for SOA-1867 - the consoles which have the SOA forms-based authentication contain <role-name>user</role-name> in their web.xml. We now have the situation where some consoles use: <role-name>JBossAdmin</role-name> and some use: <role-name>user</role-name> . Also, soa-roles.properties contains: admin=JBossAdmin,HttpInvoker,user,admin , so we have the multiple roles there too.
Based on Program discussions, this will break backward compatibility, and hence cannot be done for SOA 5.x.
Reopening because in SOA-P 5.0.0 and 5.0.1 there is <auth-constraint> <role-name>JBossAdmin</role-name> </auth-constraint> And also authentication is BASIC. How is backwards compatibility maintained by changing from what we had in 5.0.0 and 5.0.1? Excuse me if you are aware of these facts and still considered the changes to be correct. In which case feel free to close the issue again.
Fixed with revision 5855 of: build-tools/resource/soa-auth/add_security_constrain_ws.xsl Commit message: SOA-2108 Use `JBossAdmin' instead of `user' as the default role name.
Evidence of issue resolution in CR2 build - see attached files
Attachment: Added: CR1 Attachment: Added: CR2
Verified in CR2 build
Thanks Len! I also confirmed CR2 is ok but forgot about closing the JIRA.