[JBoss JIRA] (AS7-3044) bin/add-user.sh allows create two identical users
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3044?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek reopened AS7-3044:
---------------------------------
I'm not fully satisfied with present behavior.
If Realm is editable item, I can set it to something else... If so, there isn't any reason why we can't have the same user with two different realms (from admin PoV), but present behavior reject a such user (second attempt) as duplicated user.
Also it isn't a much more meaningful that although mgmt-users.properties is dedicated only for ManagementRealm, add-user script allows to add users with other realms to this file.
I think that definitive solution is set Realm in add-user script only informative (Read only) and not editable.
I'm also aware that add-user.sh isn't general tool for editing user/group/realms credentials in AS7 (compared to other JEE servers), it is suited only as simple shorthand for rights definition to Admin console - and therefore present behavior without explicit knowing this details could confuse some users too.
I think this is rather usability issue, not technical problem.
> bin/add-user.sh allows create two identical users
> -------------------------------------------------
>
> Key: AS7-3044
> URL: https://issues.jboss.org/browse/AS7-3044
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Darran Lofthouse
> Fix For: 7.1.0.CR1
>
>
> bin/add-user.sh allows to create two identical users even you specify really the same input values (realm, login name and password). It created two lines in mgmt-users.properties.
--
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
14 years, 3 months
[JBoss JIRA] (AS7-3422) @RolesAllowed @DenyAll on EJBs does not work
by G P (JIRA)
G P created AS7-3422:
------------------------
Summary: @RolesAllowed @DenyAll on EJBs does not work
Key: AS7-3422
URL: https://issues.jboss.org/browse/AS7-3422
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.CR1b
Reporter: G P
Assignee: jaikiran pai
I've a war within EJBs. Annotating an EJB method with @RolesAllowed or @DenyAll does not work as expected - method is executed even if the roles does not match.
I also added @SecurityDomain annotation, which did not change the behaviour.
EJBContext getCallerPrincipal() returns the correct (authenticated) principal, and isCallerInRole() works fine, but not @RolesAllowed
jboss-web.xml:
<jboss-web><security-domain>formauth</security-domain></jboss-web>
Here's the security-domain part of standalone.xml, which is referenced in the war:
<security-domain name="formauth" cache-type="default">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties" value="defaultUsers.properties"/>
<module-option name="rolesProperties" value="defaultRoles.properties"/>
</login-module>
</authentication>
</security-domain>
At https://community.jboss.org/message/648047 is a sample war which reproduces the defect
--
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
14 years, 3 months
[JBoss JIRA] (AS7-3435) No cloning for parameters of primitive types should be performed if 'pass-by-value' option is disabled for LocalEJBReceiver
by Alexey Makhmutov (JIRA)
Alexey Makhmutov created AS7-3435:
-------------------------------------
Summary: No cloning for parameters of primitive types should be performed if 'pass-by-value' option is disabled for LocalEJBReceiver
Key: AS7-3435
URL: https://issues.jboss.org/browse/AS7-3435
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.CR1b
Reporter: Alexey Makhmutov
Assignee: jaikiran pai
Priority: Minor
If 'pass-by-value' is disabled for the ejb client, then no cloning should be performed for parameters of primitive types. Current version of code still tries to clone them, as declared parameter class (primitive type) is not equal to runtime parameter value used during the invocation ('boxed' class for primitive type), this results a lot of cloning requests in case of remote methods with primitive types.
This problem was noticed while looking at results of profiling sampling for intensive concurrent in-vm invocations of remote methods. Despite the disabled 'pass-by-value' option and correct class-pathes for all components, profiling results still show a lot of call to cloners in case of primitive type parameters. The performance impact is not significant, however it's still additional overhead which can be avoided.
In general, I'm not sure if cloning for primitive types is required in other cases as well, however it definitely shouldn't performed if 'pass-by-value' is disabled.
--
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
14 years, 3 months