[JBoss JIRA] Commented: (JBAS-3652) Add EULA to licenses folder of distribution
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3652?page=comments#action_12343281 ]
Ryan Campbell commented on JBAS-3652:
-------------------------------------
For now, this is just for the AS itself, not libraries. This should likely go in whatever module we keep the copyright.txt file, and be copied to docs/licenses in the build/build-dist.xml.
> Add EULA to licenses folder of distribution
> -------------------------------------------
>
> Key: JBAS-3652
> URL: http://jira.jboss.com/jira/browse/JBAS-3652
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Rajesh Rajasekaran
> Priority: Critical
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt
>
>
> We need to include the attached EULA text file in all "licenses" folders of
> our distributions. It is an umbrella EULA that does not change the
> fact that our source code is open source...it simply applies a little more
> rigor around use of trademarks and logos as well as Export conditions.
> We do not need to retrofit this into existing builds, just new builds on an
> ongoing basis. Ex. JBoss AS 4.0.5 should include it.
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Commented: (JBAS-3652) Add EULA to licenses folder of distribution
by Rajesh Rajasekaran (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3652?page=comments#action_12343280 ]
Rajesh Rajasekaran commented on JBAS-3652:
------------------------------------------
Is this license used by any of the thirdparty libs, so they can be automatically pulled when downloading the thirdparty, by JBOSSBUILD.
If not i can upload to the repository and package it in the build output getting it directly from the repository.
> Add EULA to licenses folder of distribution
> -------------------------------------------
>
> Key: JBAS-3652
> URL: http://jira.jboss.com/jira/browse/JBAS-3652
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Rajesh Rajasekaran
> Priority: Critical
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt
>
>
> We need to include the attached EULA text file in all "licenses" folders of
> our distributions. It is an umbrella EULA that does not change the
> fact that our source code is open source...it simply applies a little more
> rigor around use of trademarks and logos as well as Export conditions.
> We do not need to retrofit this into existing builds, just new builds on an
> ongoing basis. Ex. JBoss AS 4.0.5 should include it.
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (SECURITY-7) Ldap*LoginModule fail to retrieve multiple role names when roleAttributeIsDN=true
by Scott M Stark (JIRA)
Ldap*LoginModule fail to retrieve multiple role names when roleAttributeIsDN=true
---------------------------------------------------------------------------------
Key: SECURITY-7
URL: http://jira.jboss.com/jira/browse/SECURITY-7
Project: JBoss Security
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.0
For a schema like example2.ldif and a configuration like:
testLdapExample22 {
org.jboss.security.auth.spi.LdapExtLoginModule
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
java.naming.provider.url="ldap://lamia/"
java.naming.security.authentication=simple
bindDN="cn=Root,dc=jboss,dc=org"
bindCredential=secret1
baseCtxDN="ou=People,o=example2,dc=jboss,dc=org"
baseFilter="(uid={0})"
rolesCtxDN="ou=Roles,o=example2,dc=jboss,dc=org";
roleFilter="(uid={0})"
roleAttributeID="memberOf"
roleAttributeIsDN="true"
roleNameAttributeID="cn"
roleRecursion=0
};
Only one role is being pulled from the cn=EchoGroup,ou=Roles,o=example2,dc=jboss,dc=org context, rather the both EchoGroup and TheDuke as only one of the cn attribute values is retrieved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Commented: (JBAS-2283) Custom header based authentication
by Anil Saldhana (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2283?page=comments#action_12343273 ]
Anil Saldhana commented on JBAS-2283:
-------------------------------------
$> ant tomcat-federation-tests
....
[junit] Running org.jboss.test.web.security.CustomHeaderAuthTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.015 sec
> Custom header based authentication
> ----------------------------------
>
> Key: JBAS-2283
> URL: http://jira.jboss.com/jira/browse/JBAS-2283
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security, Web (Tomcat) service
> Reporter: Scott M Stark
> Assigned To: Anil Saldhana
> Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.CR1
>
> Attachments: B19006.pdf, B19008v2.pdf, B19013.pdf
>
>
> We have been getting requests for custom authentication methods based around prorpietary headers/logic. The following attachments describe the oracle COREid product.
> B19006.pdf - high level overview of how the product works
> B19008v2.pdf - details of authentication protocol (p. 85 - 92)
> B19013.pdf - documentation about API
> Likely the most important part is assuming a user is who the HTTP_OBLIX_UID header says they are. The COREid server and the firewall should protect the server from unauthorized access.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Closed: (JBAS-2283) Custom header based authentication
by Anil Saldhana (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2283?page=all ]
Anil Saldhana closed JBAS-2283.
-------------------------------
Resolution: Done
> Custom header based authentication
> ----------------------------------
>
> Key: JBAS-2283
> URL: http://jira.jboss.com/jira/browse/JBAS-2283
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security, Web (Tomcat) service
> Reporter: Scott M Stark
> Assigned To: Anil Saldhana
> Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.CR1
>
> Attachments: B19006.pdf, B19008v2.pdf, B19013.pdf
>
>
> We have been getting requests for custom authentication methods based around prorpietary headers/logic. The following attachments describe the oracle COREid product.
> B19006.pdf - high level overview of how the product works
> B19008v2.pdf - details of authentication protocol (p. 85 - 92)
> B19013.pdf - documentation about API
> Likely the most important part is assuming a user is who the HTTP_OBLIX_UID header says they are. The COREid server and the firewall should protect the server from unauthorized access.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months