November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1101) Enhance the security realm plug-in mechanism for client-cert / external verification.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1101?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-764 to WFCORE-1101: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1101 (was: WFLY-764) Component/s: Domain Management Remoting Security (was: Domain Management) (was: Remoting) (was: Security) Fix Version/s: (was: Awaiting Volunteers) > Enhance the security realm plug-in mechanism for client-cert / external verification. > ------------------------------------------------------------------------------------- > > Key: WFCORE-1101 > URL: https://issues.jboss.org/browse/WFCORE-1101 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Labels: Realm_Management > > Currently verification is just based on the defined trust store - this is to take it one step further and allow an optional additional verification. > As a first step will need to ensure we have a suitable Callback from the authenticator to the realm to verify the identity and then this can be passed on to the plug-in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1100) One time password for management interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1100?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-760 to WFCORE-1100: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1100 (was: WFLY-760) Component/s: Domain Management Security (was: Domain Management) (was: Security) Fix Version/s: (was: Awaiting Volunteers) > One time password for management interfaces > ------------------------------------------- > > Key: WFCORE-1100 > URL: https://issues.jboss.org/browse/WFCORE-1100 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Labels: Common_Authentication > > This task is to look into one time password use for the management consoles. > This needs some further investigation as there is a trade off between ensuring a password is really one time and not valid for replays after use yet allowing a users web browser to keep establishing connections without forcing a new authentication every few minutes. > The native interface also needs similar consideration however the native interface does allow for connections to be kept open for a long time more naturally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1099) Utility to report on differences in domain configuration between domains

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1099?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-700 to WFCORE-1099: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1099 (was: WFLY-700) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > Utility to report on differences in domain configuration between domains > ------------------------------------------------------------------------ > > Key: WFCORE-1099 > URL: https://issues.jboss.org/browse/WFCORE-1099 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: > One of the motivations for the domain controller was to help customers manage drift in their JBoss configurations. Because of operational concerns, specifically datacenter isolation, some customers expect to need to run multiple identical domain controllers. They would then still be faced with drift across domain controllers. A utility to detect this drift would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-431) Revisit enforcement of required file system permissions.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-431?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on WFLY-431: --------------------------------------- I believe this should be moved to WildFly Core. > Revisit enforcement of required file system permissions. > -------------------------------------------------------- > > Key: WFLY-431 > URL: https://issues.jboss.org/browse/WFLY-431 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 11.0.0.Alpha1 > > > Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5613: -------------------------------------- Component/s: (was: Domain Management) Assignee: Tom Jenkinson (was: Heiko Braun) > Fix transaction subsystem resource descriptions > ----------------------------------------------- > > Key: WFLY-5613 > URL: https://issues.jboss.org/browse/WFLY-5613 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > Attachments: jts-tooltip-700.DR132.png > > > I would like ask for changing text in transaction configuration helper tooltip (_Need Help? > _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439). > Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip > Current text is > {noformat} > Default timeout: The default timeout. > Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.. > Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect. > Jts: If true this enables the Java Transaction Service. > Node identifier: Used to set the node identifier on the core environment. > Statistics enabled: Whether statistics should be enabled. > Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store. > {noformat} > {noformat} > Process id uuid: Indicates whether the transaction manager should use a UUID based process id. > Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set. > Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'. > {noformat} > {noformat} > Socket binding: Used to reference the correct socket binding to use for the recovery environment. > Status socket binding: Used to reference the correct socket binding to use for the transaction status manager. > Recovery listener: Used to specify if the recovery system should listen on a network socket or not. > {noformat} > {noformat} > Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. > Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path. > {noformat} > {noformat} > Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store > Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect. > Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect. > Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect. > Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect. > Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect. > Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect. > Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect. > {noformat} > I would propose the following changes in the tooltip text > *Attributes* > * Default timeout > ** The default timeout for a transaction managed by the transaction manager. > * Enable tsm status > ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not. > * Journal store enable async io > ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect. > * Jts > ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect. > * Node identifier > ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect. > * Statistics enabled > ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect. > * Use journal store > ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect. > *Process ID* + *Recovery* > Add information that for settings these attributes taking effect the server needs to be reloaded. > *Path* > * Object store path > ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect. > * Object store relative to > ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect. > *JDBC* > * Use jdbc store > ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect. > * Jdbc store datasource > ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect. > ...the rest of the information is ok from my point of view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5582) Can't enter an authentication module option with = (equals sign) for a security domain using the management console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5582?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5582: -------------------------------------- Assignee: (was: Brian Stansberry) > Can't enter an authentication module option with = (equals sign) for a security domain using the management console > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5582 > URL: https://issues.jboss.org/browse/WFLY-5582 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Gunnar Grim > > When editing the module options for an authentication module in a security domain, it is not possible to enter an equals sign, e g: > principalsQuery=select Password from DOIStudioUser where UserName = ? > The equals sign and anything following it is removed. > When manually editing the standalone.xml file the module option is accepted but then all options are invisible in the management console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3591) Add Keycloak authentication/authorization to http management endpoint

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3591?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-3591. ------------------------------------ Resolution: Duplicate Issue > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFLY-3591 > URL: https://issues.jboss.org/browse/WFLY-3591 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Stan Silvert > Assignee: Stan Silvert > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1095) Remove dependency on bouncycastle

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1095?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1095: ------------------------------------- Description: Core has a dependency on bouncycastle that AFAICT is not used. It was brought into core when a class from full's testsuite/shared was ported, but the core usage of the class has no need for the bouncycastle-related logic. (was: Core has a dependency on bouncycastle that AFAICT is only there so a couple string constants can be used in testsuite/shared. I'm going to try removing the methods that use the constants altogether. If that's ok (i.e. nothing fails in full's testsuite) then we'll go that route, otherwise I'll try just removing the contants imports and hard coding the strings.) > Remove dependency on bouncycastle > --------------------------------- > > Key: WFCORE-1095 > URL: https://issues.jboss.org/browse/WFCORE-1095 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Core has a dependency on bouncycastle that AFAICT is not used. It was brought into core when a class from full's testsuite/shared was ported, but the core usage of the class has no need for the bouncycastle-related logic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4966) Make sure Weld work fine outside the full feature pack

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4966?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4966: ----------------------------------- Fix Version/s: (was: 10.0.0.Final) > Make sure Weld work fine outside the full feature pack > ------------------------------------------------------ > > Key: WFLY-4966 > URL: https://issues.jboss.org/browse/WFLY-4966 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld > Reporter: Jozef Hartinger > > Review subsystem's dependencies and make them optional if appropriate. > http://lists.jboss.org/pipermail/wildfly-dev/2015-July/004202.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5450) Update to Hibernate Core 5.0.4.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5450?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5450: ----------------------------------- Summary: Update to Hibernate Core 5.0.4.Final (was: Update to Hibernate Core 5.0.2.Final) > Update to Hibernate Core 5.0.4.Final > ------------------------------------ > > Key: WFLY-5450 > URL: https://issues.jboss.org/browse/WFLY-5450 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Martin Kamp Jensen > Assignee: Jason Greene > Fix For: 10.0.0.Final > > > Please, if possible, include the latest Hibernate Core bugfix release in the final version of WildFly 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2015