November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7285) Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7285?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7285: ------------------------------- Labels: user_experience (was: ) > Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper > -------------------------------------------------------------------------------------- > > Key: WFLY-7285 > URL: https://issues.jboss.org/browse/WFLY-7285 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > > There are inconsistencies between DMR and XSD representation of {{simple-permission-mapper}}. > According to XSD both {{permission-mapping}} [1] and its inner {{permission}} [2] must occur at least one times in {{simple-permission-mapper}}. According to DMR they are {{"nillable" => true}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [2] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7288) Elytron - inconsistency between DMR and XSD representation of ldap-realm

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7288?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7288: ------------------------------- Labels: user_experience (was: ) > Elytron - inconsistency between DMR and XSD representation of ldap-realm > ------------------------------------------------------------------------ > > Key: WFLY-7288 > URL: https://issues.jboss.org/browse/WFLY-7288 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > > There are inconsistencies between DMR and XSD representation of ldap-realm. > * According to XSD [1] {{from}} attribute from user-password-mapper is required in ldap-realm. According to DMR {{from}} attribute is {{"nillable" => true}}. > * According to XSD [2] every attribute ({{algorithm-from}}, {{hash-from}}, {{seed-from}}, {{sequence-from}}) from otp-credential-mapper is required in ldap-realm. According to DMR all these attributes are {{"nillable" => true}}. > * According to XSD [3] {{name}} of {{attribute}} from new-identity-attributes is required in ldap-realm. According to DMR {{name}} of {{attribute}} is {{"nillable" => true}}. > These inconsistencies should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [2] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [3] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7286) Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7286?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7286: ------------------------------- Labels: user_experience (was: ) > Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7286 > URL: https://issues.jboss.org/browse/WFLY-7286 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > > There is an inconsistency between DMR and XSD representation of {{mechanism-provider-filtering-sasl-server-factory}}. > According to XSD [1] {{filters}} may not occur in {{mechanism-provider-filtering-sasl-server-factory}}. According to DMR {{filters}} is {{"nillable" => false}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7024) read-resource operation of jaxrs subsystem must provide more information about end-point

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7024?page=com.atlassian.jira.plugin.... ] Lin Gao updated WFLY-7024: -------------------------- Description: show-resources operation of jaxrs subsystem must provide more informations about end-point. Information about parameters and returned value should be provided. Example: {code:java} @GET @Path("entity/get") @Produces(MediaType.APPLICATION_JSON) public Person post3(@QueryParam("boolean") @DefaultValue("false") boolean v) { Person per = new Person(); per.setName("per"); per.setFamily("son"); return per; } {code} Actual return value of {{/deployment=jaxrs-eap.war/subsystem=jaxrs:show-resources}}: {noformat} { "resource-class" => "org.resteasy.simple.deployment.AdvancedService", "resource-path" => "/sample/entity/get", "resource-methods" => ["GET /jaxrs-eap/a/sample/entity/get - org.resteasy.simple.deployment.AdvancedService.post3(...)"] }, {noformat} There should be information about "boolean v" parameter and about returned type (Person). --- -jax-rs subsystem should be able to collect some statistics about invocation of end-points (count of invocations, execution time, etc.)- -Some statistics could be be activated and printed, only if end-point is also EJB bean, example:- -/subsystem=ejb3:write-attribute(name=enable-statistics,value=true)- -/deployment=cdiexp-1.0-SNAPSHOT.jar/subsystem=ejb3/stateless-session-bean=Servicer:read-resource(include-runtime=true)- *NOTE*: after discussion, the show-resources() operation is deprecated, the output should be integrated into read-resource() operation in a child resource was: show-resources operation of jaxrs subsystem must provide more informations about end-point. Information about parameters and returned value should be provided. Example: {code:java} @GET @Path("entity/get") @Produces(MediaType.APPLICATION_JSON) public Person post3(@QueryParam("boolean") @DefaultValue("false") boolean v) { Person per = new Person(); per.setName("per"); per.setFamily("son"); return per; } {code} Actual return value of {{/deployment=jaxrs-eap.war/subsystem=jaxrs:show-resources}}: {noformat} { "resource-class" => "org.resteasy.simple.deployment.AdvancedService", "resource-path" => "/sample/entity/get", "resource-methods" => ["GET /jaxrs-eap/a/sample/entity/get - org.resteasy.simple.deployment.AdvancedService.post3(...)"] }, {noformat} There should be information about "boolean v" parameter and about returned type (Person). --- -jax-rs subsystem should be able to collect some statistics about invocation of end-points (count of invocations, execution time, etc.)- -Some statistics could be be activated and printed, only if end-point is also EJB bean, example:- -/subsystem=ejb3:write-attribute(name=enable-statistics,value=true)- -/deployment=cdiexp-1.0-SNAPSHOT.jar/subsystem=ejb3/stateless-session-bean=Servicer:read-resource(include-runtime=true)- > read-resource operation of jaxrs subsystem must provide more information about end-point > ---------------------------------------------------------------------------------------- > > Key: WFLY-7024 > URL: https://issues.jboss.org/browse/WFLY-7024 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > Original Estimate: 2 days > Remaining Estimate: 2 days > > show-resources operation of jaxrs subsystem must provide more informations about end-point. Information about parameters and returned value should be provided. > Example: > {code:java} > @GET > @Path("entity/get") > @Produces(MediaType.APPLICATION_JSON) > public Person post3(@QueryParam("boolean") @DefaultValue("false") boolean v) { > Person per = new Person(); > per.setName("per"); > per.setFamily("son"); > return per; > } > {code} > Actual return value of {{/deployment=jaxrs-eap.war/subsystem=jaxrs:show-resources}}: > {noformat} > { > "resource-class" => "org.resteasy.simple.deployment.AdvancedService", > "resource-path" => "/sample/entity/get", > "resource-methods" => ["GET /jaxrs-eap/a/sample/entity/get - org.resteasy.simple.deployment.AdvancedService.post3(...)"] > }, > {noformat} > There should be information about "boolean v" parameter and about returned type (Person). > --- > -jax-rs subsystem should be able to collect some statistics about invocation of end-points (count of invocations, execution time, etc.)- > -Some statistics could be be activated and printed, only if end-point is also EJB bean, example:- > -/subsystem=ejb3:write-attribute(name=enable-statistics,value=true)- > -/deployment=cdiexp-1.0-SNAPSHOT.jar/subsystem=ejb3/stateless-session-bean=Servicer:read-resource(include-runtime=true)- > *NOTE*: after discussion, the show-resources() operation is deprecated, the output should be integrated into read-resource() operation in a child resource -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7024) read-resource operation of jaxrs subsystem must provide more information about end-point

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7024?page=com.atlassian.jira.plugin.... ] Lin Gao updated WFLY-7024: -------------------------- Summary: read-resource operation of jaxrs subsystem must provide more information about end-point (was: show-resources operation of jaxrs subsystem must provide more information about end-point) > read-resource operation of jaxrs subsystem must provide more information about end-point > ---------------------------------------------------------------------------------------- > > Key: WFLY-7024 > URL: https://issues.jboss.org/browse/WFLY-7024 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > Original Estimate: 2 days > Remaining Estimate: 2 days > > show-resources operation of jaxrs subsystem must provide more informations about end-point. Information about parameters and returned value should be provided. > Example: > {code:java} > @GET > @Path("entity/get") > @Produces(MediaType.APPLICATION_JSON) > public Person post3(@QueryParam("boolean") @DefaultValue("false") boolean v) { > Person per = new Person(); > per.setName("per"); > per.setFamily("son"); > return per; > } > {code} > Actual return value of {{/deployment=jaxrs-eap.war/subsystem=jaxrs:show-resources}}: > {noformat} > { > "resource-class" => "org.resteasy.simple.deployment.AdvancedService", > "resource-path" => "/sample/entity/get", > "resource-methods" => ["GET /jaxrs-eap/a/sample/entity/get - org.resteasy.simple.deployment.AdvancedService.post3(...)"] > }, > {noformat} > There should be information about "boolean v" parameter and about returned type (Person). > --- > -jax-rs subsystem should be able to collect some statistics about invocation of end-points (count of invocations, execution time, etc.)- > -Some statistics could be be activated and printed, only if end-point is also EJB bean, example:- > -/subsystem=ejb3:write-attribute(name=enable-statistics,value=true)- > -/deployment=cdiexp-1.0-SNAPSHOT.jar/subsystem=ejb3/stateless-session-bean=Servicer:read-resource(include-runtime=true)- -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-1912: ---------------------------------------- Can this be set on deployment and not on deploy operation? The issue which was discussed in forum is that server boots and starts deploy of MDB with @Resource dependency to queue. Deployment fails because queue is not deployed yet. Queue gets deployed later (for example after Artemis live server activates after failback and deploys all its JNDI resources like queues and connection factories to JNDI) and MDB notices it and automatically redeploys. > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFLY-7194: ------------------------------------ Can you, please, elaborate on "jvm-unportable" argument? I still don't get that. What I am suggesting here is to use implicitly {{TrustManagerFactory.getDefaultAlgorithm()}} in elytron code in case when user does not fill {{algorithm}} attribute explicitly in configuration. {{TrustManagerFactory.getDefaultAlgorithm()}} is IMO portable; on oracle java returns "SunX509" on ibm java "IbmX509". Why do you expect {{algorithm}} to change to required, once such default handling would be introduce? > Simplify creation of trust/key-manager in elytron > ------------------------------------------------- > > Key: WFLY-7194 > URL: https://issues.jboss.org/browse/WFLY-7194 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 11.0.0.Alpha1 > > > If I want to setup TLS [1], I have to create key manager with CLI command > {code} > /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509") > {code} > 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used. > 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone. > 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required. > {code} > <xs:attribute name="key-store" type="xs:string" use="optional"> > <xs:annotation> > <xs:documentation> > Reference to the KeyStore to use with the KeyManager. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > 4.{{password}} attribute is optional, probably should be required > {code} > "password" => { > "type" => STRING, > "description" => "The password to use when initialising the underlying KeyManagerFactory.", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.0.0", > "reason" => "Will be updated to use proper CredentialStore references." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-67) method-params containing an array not correctly processed for EJB2.1 with CMT

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-67?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-67: --------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1180565|https://bugzilla.redhat.com/show_bug.cgi?id=1180565] from POST to MODIFIED > method-params containing an array not correctly processed for EJB2.1 with CMT > ----------------------------------------------------------------------------- > > Key: WFLY-67 > URL: https://issues.jboss.org/browse/WFLY-67 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: JBoss 7.2.0-Final Prerelease (Commit 4ed76c) and JBoss 7.1.3.Final on Win7/64 JDK 1.7.0_09 > Reporter: Robert Panzer > Assignee: Ondrej Zizka > Fix For: 8.0.0.Alpha1 > > Attachments: cmt-never-array-params.zip > > > It seems that the method-params for container transactions are not matched correctly if the contain arrays. > I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]); > If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with > JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6) > I define the container transaction like this: > <container-transaction> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String[]</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>int</method-param> > </method-params> > </method> > <method> > <ejb-name>Second</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > </method> > <trans-attribute>Never</trans-attribute> > </container-transaction> > I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-121) Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/REMJMX-121?page=com.atlassian.jira.plugin... ] Farah Juma updated REMJMX-121: ------------------------------ Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/24 > Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: REMJMX-121 > URL: https://issues.jboss.org/browse/REMJMX-121 > Project: Remoting JMX > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 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 2016