January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6399) Elytron integration with naming subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6399?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-6399. ------------------------------------ Resolution: Rejected No Elytron specific integration required within the naming subsystem. > Elytron integration with naming subsystem > ----------------------------------------- > > Key: WFLY-6399 > URL: https://issues.jboss.org/browse/WFLY-6399 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > External contexts look likely to need some integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6400) Elytron integration with resource adapters subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6400?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6400: ----------------------------------- Component/s: Security > Elytron integration with resource adapters subsystem > ---------------------------------------------------- > > Key: WFLY-6400 > URL: https://issues.jboss.org/browse/WFLY-6400 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6400) Elytron integration with resource adapters subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6400?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6400: -------------------------------------- Assignee: Stefano Maestri (was: Darran Lofthouse) > Elytron integration with resource adapters subsystem > ---------------------------------------------------- > > Key: WFLY-6400 > URL: https://issues.jboss.org/browse/WFLY-6400 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Stefano Maestri > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6401) Elytron integration with the webservices subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6401?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6401: ----------------------------------- Component/s: Security > Elytron integration with the webservices subsystem > -------------------------------------------------- > > Key: WFLY-6401 > URL: https://issues.jboss.org/browse/WFLY-6401 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6401) Elytron integration with the webservices subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6401?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6401: -------------------------------------- Assignee: Alessio Soldano (was: Darran Lofthouse) > Elytron integration with the webservices subsystem > -------------------------------------------------- > > Key: WFLY-6401 > URL: https://issues.jboss.org/browse/WFLY-6401 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Darran Lofthouse > Assignee: Alessio Soldano > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6823?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6823: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > ----------------------------------------------------------------------------------------- > > Key: WFLY-6823 > URL: https://issues.jboss.org/browse/WFLY-6823 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603. > We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any information about it in specification. > It works with Chrome and Opera, but it doesn't work with Firefox. > Since there is no documentation for this username/password limitation it can affect customers who want to use non-ASCII credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6835) Vault.sh misleading output

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6835?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6835: -------------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Vault.sh misleading output > -------------------------- > > Key: WFLY-6835 > URL: https://issues.jboss.org/browse/WFLY-6835 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Peter Skopek > Priority: Minor > > Vault.sh advise to insert vault xml snippet as follows: > {code} > Vault Configuration in AS7 config file: > ******************************************** > ... > </extensions> > <vault> > <vault-option name="KEYSTORE_URL" value="EAP_HOME/vault/vault.keystore"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-5dOaAVafCSd"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="1234abcd"/> > <vault-option name="ITERATION_COUNT" value="120"/> > <vault-option name="ENC_FILE_DIR" value="EAP_HOME/vault/"/> > </vault><management> ... > ******************************************** > {code} > 1. User can insert this snippet on wrong place. See forum link for example. Pobably CLI command would be more suitable? > {code} > /core-service=vault:add(vault-options=[("KEYSTORE_URL" => "PATH_TO_KEYSTORE"),("KEYSTORE_PASSWORD" => "MASKED_PASSWORD"),("KEYSTORE_ALIAS" => "ALIAS"),("SALT" => "SALT"),("ITERATION_COUNT" => "ITERATION_COUNT"),("ENC_FILE_DIR" => "ENC_FILE_DIR")]) > {code} > 2. There is still reference to AS7 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7104) Elytron properties-realm enforces REALM_NAME comment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7104?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7104: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Elytron properties-realm enforces REALM_NAME comment > ---------------------------------------------------- > > Key: WFLY-7104 > URL: https://issues.jboss.org/browse/WFLY-7104 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Elytron enforces existence of {{"#$REALM_NAME=...$"}} comment in property file referenced from properties-realms. > When using legacy security and this line is missing, server starts without error. > *Expected behavior:* > Elytron's properties-realm *doesn't require* this comment. If the comment is present, it *may* verify if its content fits the realm name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7040) Add a set of tests for HTTP authentication when backed by Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7040?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7040: -------------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Add a set of tests for HTTP authentication when backed by Elytron > ----------------------------------------------------------------- > > Key: WFLY-7040 > URL: https://issues.jboss.org/browse/WFLY-7040 > Project: WildFly > Issue Type: Task > Components: Test Suite, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7125) Required attributes of elytron key-store creation add operation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7125?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7125: ----------------------------------- Summary: Required attributes of elytron key-store creation add operation (was: Required attributes of elytron key-store creation CLI command) > Required attributes of elytron key-store creation add operation > --------------------------------------------------------------- > > Key: WFLY-7125 > URL: https://issues.jboss.org/browse/WFLY-7125 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Minimal CLI command to create key store is > {code} > /subsystem=elytron/key-store=server:add(type="JKS") > {code} > But it has these problems: > * Password attribute has to be required. I can't think of case when that could be ommited. > * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017