[JBoss JIRA] (AS7-2267) The Console logs the DMR commands
by Rich Raposa (Created) (JIRA)
The Console logs the DMR commands
---------------------------------
Key: AS7-2267
URL: https://issues.jboss.org/browse/AS7-2267
Project: Application Server 7
Issue Type: Feature Request
Reporter: Rich Raposa
It would be nice if changes made to the configuration file via the Console were logged in DMR format so that the commands could be executed as a CLI script.
A simpler option would be to provide a link next to a resource that shows the CLI command you would use to create that resource. For example, in the list of datasources on the Datasources Configuration tab, next to each datasource would be a link that would contain the CLI command for defining that datasource.
The use case is this: I can take advantage of the ease-of-use of the Console to define a resource, then copy-and-paste the CLI command to define a script so that the resource can be defined over and over again on all of my EAP deployments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-1913) Add script to simplify creating the password hashes
by Darran Lofthouse (JIRA)
Add script to simplify creating the password hashes
---------------------------------------------------
Key: AS7-1913
URL: https://issues.jboss.org/browse/AS7-1913
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management, Security
Environment:
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
When enabling pre-digested passwords administrators will require a way to generate the hashes, generation is simple however we should also publish a script so they don't need to spend time setting up their own generation if they don't need to.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-1838) Add support for pre-digested passwords to AS7 domain realms
by Darran Lofthouse (JIRA)
Add support for pre-digested passwords to AS7 domain realms
-----------------------------------------------------------
Key: AS7-1838
URL: https://issues.jboss.org/browse/AS7-1838
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
Storing plain text passwords means that should the file containing these passwords be compromised not only could the passwords be used to access the AS instance they were using the passwords could potentially be used for any systems secured with the same passwords.
The pre-digested passwords will be digested with the username, password and realm - this will mean that although they still need to be kept secure to prevent access to the AS instance they secure they will not be useful for gaining access to different systems secured with different realms.
(As backwards compatibility is to be retained AS 7.0.2 will have this feature switched off by default leaving the end user to choose to switch it on - for AS 7.1.0 this will be reversed making it the default for out of the box)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
by Darran Lofthouse (JIRA)
Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Alpha1
It is reported that the realm used for the endpoint needs to match the endpoint name - for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the user of the realm they are using. This may also need expanding to multiple realms in the future so users in different realms can all authenticate against the same resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-2104) TS: Pick the most acceptable test packages organization
by Ondrej Zizka (Created) (JIRA)
TS: Pick the most acceptable test packages organization
-------------------------------------------------------
Key: AS7-2104
URL: https://issues.jboss.org/browse/AS7-2104
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
1) Split classes to src/main and src/test ?
This seems to be decided before - integration tests suite has all classes in src/test.
{quote}
(02:35:15) barreiro: When I start I done it that way so that it clear to me what was the test code, the test subject and the resources --- I knew that probably I would have to change the location later.
{quote}
2) Low-level Test packages micro
{quote}
(02:37:51) barreiro: should I create one sub package for each test --- like /web/xxxTestCase --- or stick with the old schema of having web/tests and web/servlets, ... etc.
(02:38:01) ozizka: Not sure if democracy is the principle to follow here, but I'd like devs to agree upon these things. TBD next week
(02:38:41) ozizka: Depends if you reuse them.
(02:39:24) ozizka: But generally, I'd prefer the first approach -
(02:39:53) ozizka: with reused things being placed one level higher, or next to
(02:40:16) ozizka: The structure should reflect test's structure
(02:40:24) barreiro: IMO, democracy is not the way to go in a OSS project :P ... I'll do it the way you ask me to ;)
(02:40:34) ozizka: Ok :)
(02:40:57) ozizka: But anyway - what's your preference?
(02:41:07) ozizka: Or what would suite better for _your_ case
(02:42:42) barreiro: the ultimate goal is that someone from outside can easily understand what's going on. Like me, I just landed in this project. :P
(02:43:58) barreiro: surely that it should reflect the test's structure. but I would rather have a common structure in most modules ...
(02:45:30) barreiro: like, at some level there is a clear list of the tests in the package that is not mixed with other stuff --- be it a list of packages or a test package with all the test classes
(02:45:43) ozizka: Well, 1st option is current practice, I'd stick with that.
(02:46:47) barreiro: and from there should be clear (as possible) what resources are used.
(02:47:34) ozizka: I was thinking about using a mechanism used in Wicket framework, if you know that,
(02:47:57) ozizka: which is, having a mechanism to load resources from places
(02:48:04) barreiro: After a while I start to understand how AS6 is structured ... the problem is that there is too much voodoo in the back that defeats it's purpose.
(02:48:18) ozizka: where the test class is loaded, or it's superclass, etc.
(02:48:45) ozizka: Eventually it could go by packages up. But perhaps too magical for a testsuite
(02:49:10) ozizka: Right. That's the voodoo.
(02:56:27) barreiro: yep. Shrinkwrap and arquilling are great for that. The magic is greatly reduced, without adding much complexity.
(02:58:10) ozizka: One other argument to have the package-per-test separation is that if we decided the other way, moving the files would be easier
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months