[JBoss JIRA] (SECURITY-711) LdapExtAdLoginModule proposal for inclusion
by Péter Radics (JIRA)
[ https://issues.jboss.org/browse/SECURITY-711?page=com.atlassian.jira.plug... ]
Péter Radics updated SECURITY-711:
----------------------------------
Attachment: picketbox-r362-LdapExtAdLoginModule.patch
patch that adds LdapExtAdLoginModule
> LdapExtAdLoginModule proposal for inclusion
> -------------------------------------------
>
> Key: SECURITY-711
> URL: https://issues.jboss.org/browse/SECURITY-711
> Project: PicketBox
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Components: PicketBox, Security SPI
> Affects Versions: PicketBox_4_0_14.Final
> Environment: jboss7, active directory authentication
> Reporter: Péter Radics
> Assignee: Anil Saldhana
> Priority: Minor
> Labels: LdapExtLoginModule, active-directory, security
> Attachments: picketbox-r362-LdapExtAdLoginModule.patch
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Please consider including the attached LdapExtAdLoginModule into the official release. This login module is based on r362 of LdapExtLoginModule, but it's better suited for deeply nested Active Directory domains: it only uses one search for the userDN then it's resolving the roles recursively by querying attributes on DNs only. (as a side-effect, it doesn't trigger AS7-5737)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (SECURITY-711) LdapExtAdLoginModule proposal for inclusion
by Péter Radics (JIRA)
Péter Radics created SECURITY-711:
-------------------------------------
Summary: LdapExtAdLoginModule proposal for inclusion
Key: SECURITY-711
URL: https://issues.jboss.org/browse/SECURITY-711
Project: PicketBox
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: PicketBox, Security SPI
Affects Versions: PicketBox_4_0_14.Final
Environment: jboss7, active directory authentication
Reporter: Péter Radics
Assignee: Anil Saldhana
Priority: Minor
Attachments: picketbox-r362-LdapExtAdLoginModule.patch
Please consider including the attached LdapExtAdLoginModule into the official release. This login module is based on r362 of LdapExtLoginModule, but it's better suited for deeply nested Active Directory domains: it only uses one search for the userDN then it's resolving the roles recursively by querying attributes on DNs only. (as a side-effect, it doesn't trigger AS7-5737)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (SECURITY-710) Vault : if the storepass is not equal to the keypass, the exception "PB00019: Processing Failed:Unable to get Keystore" is raised
by guillaume cornet (JIRA)
guillaume cornet created SECURITY-710:
-----------------------------------------
Summary: Vault : if the storepass is not equal to the keypass, the exception "PB00019: Processing Failed:Unable to get Keystore" is raised
Key: SECURITY-710
URL: https://issues.jboss.org/browse/SECURITY-710
Project: PicketBox
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: guillaume cornet
Assignee: Anil Saldhana
vault.sh terminates on error "Exception encountered:PB00019: Processing Failed:Unable to get Keystore:" when the storepass and the keypass are differents.
I beleive this behavior is caused by a bug in the method org.picketbox.plugins.vault.PicketBoxSecurityVault.init(Map<String, Object> options).
I'm using picketbox 4.0.9, which contains the following code :
package org.picketbox.plugins.vault;
...
class PicketBoxSecurityVault ... {
...
public void init(Map<String, Object> options) throws SecurityVaultException
{
...
keystore = KeyStoreUtil.getKeyStore(keystoreURL, keystorePass.toCharArray());
keypair = KeyStoreUtil.getPrivateKey(keystore, alias, keystorePass.toCharArray());
...
}
...
As you can see, this code loads the store (e.g. 'getKeyStore()') and the key (e.g. 'getPrivateKey()') with the same password (e.g. 'keystorePass') ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6144) Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6144?page=com.atlassian.jira.plugin.s... ]
Scott Marlow closed AS7-6144.
-----------------------------
> Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6144
> URL: https://issues.jboss.org/browse/AS7-6144
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Environment: JBoss AS 7.1.2.Final, Hibernate 4.1.2.Final
> Reporter: Marek Posolda
> Assignee: Scott Marlow
>
> Normally UserTransaction is available in JBoss via JNDI lookup to "java:comp/UserTransaction" . But sometimes this approach does not work (For example if we have custom worker threads in our application or we are starting our AS7 deployment with custom MSC thread before "java:comp" context is available to JNDI)
> So it may be good to fallback to "java:jboss/UserTransaction", which is available in JBoss AS7 even from custom threads.
> Is it possible to change "org.jboss.as.jpa.hibernate4.JBossAppServerJtaPlatform" or "org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform" to have method locateUserTransaction() similar to this?:
> {code}
> public static final String AS7_NEW_UT_NAME = "java:jboss/UserTransaction";
> @Override
> protected UserTransaction locateUserTransaction() {
> try {
> return (UserTransaction) jndiService().locate(UT_NAME);
> }
> catch(JndiException jndiException) {
> return (UserTransaction) jndiService().locate(AS7_NEW_UT_NAME);
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6128) In domain mode after some CLI I was not able to restart a particular host until..
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-6128?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber commented on AS7-6128:
------------------------------------------
If you see something hanging or not responding it would be helpful in general to get a thread-dump [1] of the java process(es).
[1] https://community.jboss.org/wiki/ThreadDump
> In domain mode after some CLI I was not able to restart a particular host until..
> ---------------------------------------------------------------------------------
>
> Key: AS7-6128
> URL: https://issues.jboss.org/browse/AS7-6128
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Environment: Linux and EAP 6
> Reporter: Jim Tyrrell
> Assignee: Brian Stansberry
>
> Running the examples in the JB348 Admin II class around the CLI section I uncovered an odd error, that I was not able to reproduce, and no one else seemed to have, but I thought I should log it here.
> In the class last week I was doing the CLI activities per the guide on a domain instance. I fat fingered a bunch of things, and was getting errors. Once I was done making the changes with any errors I tried to restart host1 in the web console. This errored out without a good error message. After a few times of that I tried cntrl-cing in the console, only to have the server shutdown after about 5 minutes or so of hitting cntrl-c. I did not notice any error messages, but it makes me think some sort of racing, or locking condition exists in domain mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6134) Problem reassigning server to different group
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber commented on AS7-6134:
------------------------------------------
Hmm, am i missing something? I am doing this:
{noformat}
[domain@localhost:9999 /] /host=master/server-config=server-one:stop
{
"outcome" => "success",
"result" => "STOPPING"
}
[domain@localhost:9999 /] batch
[domain@localhost:9999 / #] /host=master/server-config=server-one:write-attribute(name=group,value=other-server-group)
#1 /host=master/server-config=server-one:write-attribute(name=group,value=other-server-group)
[domain@localhost:9999 / #] run-batch
The batch executed successfully
[domain@localhost:9999 /] /host=master/server-config=server-one:read-resource
{
"outcome" => "success",
"result" => {
"auto-start" => true,
"cpu-affinity" => undefined,
"group" => "other-server-group",
"interface" => undefined,
"jvm" => undefined,
"name" => "server-one",
"path" => undefined,
"priority" => undefined,
"socket-binding-group" => undefined,
"socket-binding-port-offset" => 0,
"system-property" => undefined
}
}
[domain@localhost:9999 /] /host=master/server-config=server-one:start
{
"outcome" => "success",
"result" => "STARTING"
}
[domain@localhost:9999 /] batch
[domain@localhost:9999 / #] /host=master/server-config=server-one:write-attribute(name=group,value=main-server-group)
#1 /host=master/server-config=server-one:write-attribute(name=group,value=main-server-group)
[domain@localhost:9999 / #] run-batch
The batch executed successfully
[domain@localhost:9999 /] /host=master/server-config=server-one:read-resource
{
"outcome" => "success",
"result" => {
"auto-start" => true,
"cpu-affinity" => undefined,
"group" => "main-server-group",
"interface" => undefined,
"jvm" => undefined,
"name" => "server-one",
"path" => undefined,
"priority" => undefined,
"socket-binding-group" => undefined,
"socket-binding-port-offset" => 0,
"system-property" => undefined
}
}
[domain@localhost:9999 /]
{noformat}
> Problem reassigning server to different group
> ---------------------------------------------
>
> Key: AS7-6134
> URL: https://issues.jboss.org/browse/AS7-6134
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Emanuel Muckenhuber
> Fix For: 7.2.0.CR1
>
>
> I cannot reassign a (stopped) server to a different group if the domain has two members
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6160) Missing isDefined() check on wsdl-host configuration element
by Alessio Soldano (JIRA)
Alessio Soldano created AS7-6160:
------------------------------------
Summary: Missing isDefined() check on wsdl-host configuration element
Key: AS7-6160
URL: https://issues.jboss.org/browse/AS7-6160
Project: Application Server 7
Issue Type: Feature Request
Components: Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 7.2.0.Alpha1
WSSubsystemAdd builds the WS server config using data from AS model; when reading the ModelNode for wsdl-host conf element from the webservices subsystem configuration, that should be checked with isDefined() to pass null instead of "undefined" into the WS server config.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months