November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-726) Default Mechanism Ordering Implementation

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-726?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-726: --------------------------------- Maybe now is the time for OpenSSL-style selection strings for SASL mechs? > Default Mechanism Ordering Implementation > ----------------------------------------- > > Key: ELY-726 > URL: https://issues.jboss.org/browse/ELY-726 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta13 > > > We have to have some form of mechanism ordering anyway to get silent mechanisms to the front of the queue. > SaslMechanismInformation may need some updates but we have plenty of information about the mechanisms so we should be able to put together a reasonable documented ordering. > Stronger mechanisms that can complete without interaction with the client can be pulled up the list as they can quickly silently fail where AuthenticationClient does not have enough information to handle them. This set probably includes JBOSS_LOCAL_USER, EXTERNAL, GSSAPI, GS2, and the token mechs. > For username / password mechanisms we can ensure PLAIN goes last. > Of the CRAM, Digest, and SCRAM set I would suggest first order by digest algorithm and then SCRAM -> Digest -> CRAM. > There will be the opportunity for plenty of discussions on is X really better than Y but I think a reasonable default implementation that is documented will be much better than today's current random ordering. Once filtering has been applied to take into account things like available credentials in the realms etc. > I would expect most lists to be very small, maybe some silent mechs a token mech and one or two username / password mechs depending on consistency of an identity store. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7454) Incorrect description of remove operation on mail session

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7454?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-7454: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Tomaz Cerar) > Incorrect description of remove operation on mail session > --------------------------------------------------------- > > Key: WFLY-7454 > URL: https://issues.jboss.org/browse/WFLY-7454 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 10.1.0.Final > Reporter: Radim Hatlapatka > Assignee: Dmitrii Tikhomirov > Labels: user_experience > > {{/subsystem=mail/mail-session=default:read-operation-description(name=remove)}} description says that it is about adding mail session, which is incorrect, it should be about removing mail session. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-726) Default Mechanism Ordering Implementation

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-726: ------------------------------------ Summary: Default Mechanism Ordering Implementation Key: ELY-726 URL: https://issues.jboss.org/browse/ELY-726 Project: WildFly Elytron Issue Type: Task Components: SASL Reporter: Darran Lofthouse Fix For: 1.1.0.Beta13 We have to have some form of mechanism ordering anyway to get silent mechanisms to the front of the queue. SaslMechanismInformation may need some updates but we have plenty of information about the mechanisms so we should be able to put together a reasonable documented ordering. Stronger mechanisms that can complete without interaction with the client can be pulled up the list as they can quickly silently fail where AuthenticationClient does not have enough information to handle them. This set probably includes JBOSS_LOCAL_USER, EXTERNAL, GSSAPI, GS2, and the token mechs. For username / password mechanisms we can ensure PLAIN goes last. Of the CRAM, Digest, and SCRAM set I would suggest first order by digest algorithm and then SCRAM -> Digest -> CRAM. There will be the opportunity for plenty of discussions on is X really better than Y but I think a reasonable default implementation that is documented will be much better than today's current random ordering. Once filtering has been applied to take into account things like available credentials in the realms etc. I would expect most lists to be very small, maybe some silent mechs a token mech and one or two username / password mechs depending on consistency of an identity store. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7500) Upgrade Apache CXF from 3.1.6 to 3.1.8

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-7500: ------------------------------------- Summary: Upgrade Apache CXF from 3.1.6 to 3.1.8 Key: WFLY-7500 URL: https://issues.jboss.org/browse/WFLY-7500 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1918) re-enable quote parsing

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1918?page=com.atlassian.jira.plugi... ] Marek Kopecký commented on WFCORE-1918: --------------------------------------- [~jdenise]: In my point of view, this is good solution: # parse ' and " and display the '>' prompt if ' or " are not escaped (\' or \") and if ' and " are not closed # Do not parse the ' and " when they are located in comment (a line that starts with #) > re-enable quote parsing > ----------------------- > > Key: WFCORE-1918 > URL: https://issues.jboss.org/browse/WFCORE-1918 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha11 > Reporter: Hisanobu Okuda > Assignee: Jean-Francois Denise > > The fix for WFCORE-1804 was committed [here|https://github.com/wildfly/wildfly-core/commit/027bfe959988b25e45771...]. > It has a side-effect that it disables quote parsing. Now the [another fix|https://github.com/aeshell/aesh/commit/0e8aa5cf514d5af81b16f7741c92a6...] which does not have the side-effect was committed in [aesh|https://github.com/aeshell/aesh]. The following line in the [previous fix|ttps://github.com/wildfly/wildfly-core/commit/027bfe959988b25e4577149...] should be removed, when the new aesh version is released (0.66.11 or 12?). > ??cli/src/main/java/org/jboss/as/cli/impl/CommandContextImpl.java:495?? > {code} > settings.parsingQuotes(false); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1356) Advance PseudoClock in KIE-Server/Decision Server

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1356?page=com.atlassian.jira.plugi... ] Duncan Doyle reassigned DROOLS-1356: ------------------------------------ Assignee: Matteo Mortari (was: Edson Tirelli) > Advance PseudoClock in KIE-Server/Decision Server > ------------------------------------------------- > > Key: DROOLS-1356 > URL: https://issues.jboss.org/browse/DROOLS-1356 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 7.0.0.Beta2 > Environment: JBoss BRMS 6.4.0, macOS 10.11.1, Oracle Hotspot 1.8.0_101 > Reporter: Duncan Doyle > Assignee: Matteo Mortari > > KIE-Server does not provide a command to advance the time of a pseudo-clock. This functionality is required (or at least, highly useful) when KIE-Server is used for CEP sessions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1356) Advance PseudoClock in KIE-Server/Decision Server

by Duncan Doyle (JIRA)

Duncan Doyle created DROOLS-1356: ------------------------------------ Summary: Advance PseudoClock in KIE-Server/Decision Server Key: DROOLS-1356 URL: https://issues.jboss.org/browse/DROOLS-1356 Project: Drools Issue Type: Feature Request Components: kie server Affects Versions: 7.0.0.Beta2 Environment: JBoss BRMS 6.4.0, macOS 10.11.1, Oracle Hotspot 1.8.0_101 Reporter: Duncan Doyle Assignee: Edson Tirelli KIE-Server does not provide a command to advance the time of a pseudo-clock. This functionality is required (or at least, highly useful) when KIE-Server is used for CEP sessions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7499) Elytron "expressions-allowed" => false attributes

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7499?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7499: ------------------------------- Labels: user_experience (was: ) > Elytron "expressions-allowed" => false attributes > ------------------------------------------------- > > Key: WFLY-7499 > URL: https://issues.jboss.org/browse/WFLY-7499 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Labels: user_experience > > Please change these attributes to {{"expressions-allowed" => true}} if reasonable > {code} > /configurable-sasl-server-factory/protocol > /configurable-sasl-server-factory/server-name > /filesystem-realm/levels > /token-realm/public-key > /token-realm/principal-claim > /token-realm/oauth2-introspection/host-name-verification-policy > /token-realm/oauth2-introspection/introspection-url > /token-realm/oauth2-introspection/client-secret > /token-realm/oauth2-introspection/client-id > /token-realm/oauth2-introspection/public-key > /token-realm/oauth2-introspection/token-realm > /jdbc-realm/principal-query/sql > /jdbc-realm/principal-query/data-source > /jdbc-realm/clear-password-mapper/password-index > /jdbc-realm/bcrypt-mapper/password-index > /jdbc-realm/bcrypt-mapper/salt-index > /jdbc-realm/bcrypt-mapper/iteration-count-index > /jdbc-realm/salted-simple-digest-mapper/algorithm > /jdbc-realm/salted-simple-digest-mapper/password-index > /jdbc-realm/salted-simple-digest-mapper/salt-index > /jdbc-realm/simple-digest-mapper/password-index > /jdbc-realm/scram-mapper/algorithm > /jdbc-realm/scram-mapper/password-index > /jdbc-realm/scram-mapper/salt-index > /jdbc-realm/scram-mapper/iteration-count-index > /security-domain/default-realm > These applies to key-store and key-manager: > */credential-reference/store > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} > These are not marked as capability reference. But seems referencing another service, so not sure if it is issue in these cases: > * /jdbc-realm/principal-query/data-source > * /security-domain/default-realm > * /credential-reference/store -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7499) Elytron "expressions-allowed" => false attributes

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7499?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-6936 to WFLY-7499: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7499 (was: JBEAP-6936) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) (was: User Experience) Target Release: (was: 7.1.0.GA) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR7) > Elytron "expressions-allowed" => false attributes > ------------------------------------------------- > > Key: WFLY-7499 > URL: https://issues.jboss.org/browse/WFLY-7499 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > > Please change these attributes to {{"expressions-allowed" => true}} if reasonable > {code} > /configurable-sasl-server-factory/protocol > /configurable-sasl-server-factory/server-name > /filesystem-realm/levels > /token-realm/public-key > /token-realm/principal-claim > /token-realm/oauth2-introspection/host-name-verification-policy > /token-realm/oauth2-introspection/introspection-url > /token-realm/oauth2-introspection/client-secret > /token-realm/oauth2-introspection/client-id > /token-realm/oauth2-introspection/public-key > /token-realm/oauth2-introspection/token-realm > /jdbc-realm/principal-query/sql > /jdbc-realm/principal-query/data-source > /jdbc-realm/clear-password-mapper/password-index > /jdbc-realm/bcrypt-mapper/password-index > /jdbc-realm/bcrypt-mapper/salt-index > /jdbc-realm/bcrypt-mapper/iteration-count-index > /jdbc-realm/salted-simple-digest-mapper/algorithm > /jdbc-realm/salted-simple-digest-mapper/password-index > /jdbc-realm/salted-simple-digest-mapper/salt-index > /jdbc-realm/simple-digest-mapper/password-index > /jdbc-realm/scram-mapper/algorithm > /jdbc-realm/scram-mapper/password-index > /jdbc-realm/scram-mapper/salt-index > /jdbc-realm/scram-mapper/iteration-count-index > /security-domain/default-realm > These applies to key-store and key-manager: > */credential-reference/store > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} > These are not marked as capability reference. But seems referencing another service, so not sure if it is issue in these cases: > * /jdbc-realm/principal-query/data-source > * /security-domain/default-realm > * /credential-reference/store -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7498) Elytron Credential Store "base.store" parameter doesn't work properly.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7498?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-7498: ---------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Elytron Credential Store "base.store" parameter doesn't work properly. > ---------------------------------------------------------------------- > > Key: WFLY-7498 > URL: https://issues.jboss.org/browse/WFLY-7498 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > Elytron Credential Store "base.store" parameter doesn't work properly. > I tried create credential store from scratch: > {code} > /subsystem=elytron/credential-store=cs001_sb:add(uri="cr-store://test/key126.jceks?store.password=pass123;key.password=pass456;create.storage=true; > store.base=/tmp;key.alias=MY_ALIAS") > {code} > {code} > /subsystem=elytron/credential-store=cs001_sb/alias=alias001:add(secret-value=secValue) > {code} > and credential store file *is created in JBOSS_EAP/Standalone/data path not in /tmp.* > *My investigation* > * Here it seems fine https://github.com/wildfly-security/wildfly-elytron/blob/0f0e0109c2652fdc... > * Maybe some kind of compiler optimisation (switch line execution?) https://github.com/wildfly-security/wildfly-elytron/blob/0f0e0109c2652fdc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2016