November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7432) Elytron key-store requires set credential-reference which is wrongly marked as optional.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7432?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-7432: ------------------------------- Summary: Elytron key-store requires set credential-reference which is wrongly marked as optional. (was: Elytron KeyStore requires set CredentialReference which is optional.) > Elytron key-store requires set credential-reference which is wrongly marked as optional. > ---------------------------------------------------------------------------------------- > > Key: WFLY-7432 > URL: https://issues.jboss.org/browse/WFLY-7432 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > In EAP7.1.0.DR7 keystore uses credentialReference with clear-text attribute for password instead of password attribute. > But there is problem with credential reference element which is optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7432) Elytron KeyStore requires set CredentialReference which is optional.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7432?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-7432: ------------------------------- Summary: Elytron KeyStore requires set CredentialReference which is optional. (was: KeyStore requires set CredentialReference which is optional.) > Elytron KeyStore requires set CredentialReference which is optional. > -------------------------------------------------------------------- > > Key: WFLY-7432 > URL: https://issues.jboss.org/browse/WFLY-7432 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > In EAP7.1.0.DR7 keystore uses credentialReference with clear-text attribute for password instead of password attribute. > But there is problem with credential reference element which is optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7432) KeyStore requires set CredentialReference which is optional.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7432?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-7432: ------------------------------- Description: In EAP7.1.0.DR7 keystore uses credentialReference with clear-text attribute for password instead of password attribute. But there is problem with credential reference element which is optional. Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 was: In EAP7.1.0.DR7 keystore uses credentialReference with clear-text attribute for password instead of password attribute. But there is problem with credential reference element which is optional. *Scenario:* I want to create KeyStore with minimum required settings. But this CLI command */subsystem=elytron/key-store=keyStore:add(type=JKS)* ends with error { "outcome" => "failed", "failure-description" => { "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.org.jboss.as.controller.security.CredentialReference"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.key-store.keyStore is missing [org.wildfly.security.credential-store-client.org.jboss.as.controller.security.CredentialReference]"] }, "rolled-back" => true } Resource description says this {code} "credential-reference" => { "type" => OBJECT, "description" => "The reference to credential stored in CredentialStore under defined alias or clear text password.", "expressions-allowed" => false, "nillable" => true, "value-type" => { "store" => { "type" => STRING, "description" => "The name of the credential store holding the alias to credential.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L }, "alias" => { "type" => STRING, "description" => "The alias which denotes stored secret or credential in the store.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L }, "type" => { "type" => STRING, "description" => "The type of credential this reference is denoting.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L }, "clear-text" => { "type" => STRING, "description" => "Secret specified using clear text. Check credential store way of supplying credential/secrets to services.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L } }, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} *NOTE* EAP7.1.0.DR6 works fine with "password" attribute. > KeyStore requires set CredentialReference which is optional. > ------------------------------------------------------------ > > Key: WFLY-7432 > URL: https://issues.jboss.org/browse/WFLY-7432 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > In EAP7.1.0.DR7 keystore uses credentialReference with clear-text attribute for password instead of password attribute. > But there is problem with credential reference element which is optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7219) Wrong description of missing target-name in simple-permission-mapper

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7219?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7219: ------------------------------- Labels: user_experience (was: ) > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: WFLY-7219 > URL: https://issues.jboss.org/browse/WFLY-7219 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[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)

7 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)

7 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)

7 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)

7 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)

7 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)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2016