November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-681) Hide private packages from generated javadoc.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-681?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-681: --------------------------------- Fix Version/s: 1.1.0.Beta13 (was: 1.1.0.Beta12) > Hide private packages from generated javadoc. > --------------------------------------------- > > Key: ELY-681 > URL: https://issues.jboss.org/browse/ELY-681 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta13 > > > We may want two profiles so we can generate a full javadoc and a 'public' javadoc. > The 'public' javadoc should be the default one generated and should exclude the following packages: - > org.wildfly.security._private > org.wildfly.security.asn1 > org.wildfly.security.auth.realm > org.wildfly.security.auth.realm.* > org.wildfly.security.authz.jacc > org.wildfly.security.credential.store.impl > org.wildfly.security.security.digest > org.wildfly.security.http.impl > org.wildfly.security.security.keystore > org.wildfly.security.mechanism.oauth2 > org.wildfly.security.mechanism.scram > org.wildfly.security.password.impl > org.wildfly.security.password.util > org.wildfly.security.pem > org.wildfly.security.sasl > org.wildfly.security.sasl.* (Except util) > org.wildfly.security.util > org.wildfly.security.util_private > org.wildfly.security.x500 > org.wildfly.security.x500.cert -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-705) Release WildFly Elytron 1.1.0.Beta12

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-705?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-705. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta12 > ------------------------------------ > > Key: ELY-705 > URL: https://issues.jboss.org/browse/ELY-705 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta12 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1916) Upgrade to WildFly Elytron 1.1.0.Beta12

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1916: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta12 Key: WFCORE-1916 URL: https://issues.jboss.org/browse/WFCORE-1916 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha12 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7436: ----------------------------------- Assignee: Ilia Vassilev (was: Jan Kalina) > Some attributes in Elytron ldap-realm are nillable=false but have set default values > ------------------------------------------------------------------------------------ > > Key: WFLY-7436 > URL: https://issues.jboss.org/browse/WFLY-7436 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > > Following attributes Elytron ldap-realm are nillable=false but have set default values: > * {{identity-mapping.use-recursive-search}} > * {{identity-mapping.user-password-mapper.writable}} > * {{identity-mapping.user-password-mapper.verifiable}} > Using nillable=false with set default value can be confused (because default value should be used in case when none value is set and nillable=false says that any value must by used). > Suggestion: > Since none of these mentioned attributes is required by CLI commands set nillable for these attributes to true. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1344) Add documentation for Aries-Blueprint integration

by Kartikeya Dwivedi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1344?page=com.atlassian.jira.plugi... ] Kartikeya Dwivedi commented on DROOLS-1344: ------------------------------------------- Thanks [~mfusco]! > Add documentation for Aries-Blueprint integration > ------------------------------------------------- > > Key: DROOLS-1344 > URL: https://issues.jboss.org/browse/DROOLS-1344 > Project: Drools > Issue Type: Task > Components: docs > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1525) ageout-history does not report failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1525?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1525: ------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1331586|https://bugzilla.redhat.com/show_bug.cgi?id=1331586] from POST to MODIFIED > ageout-history does not report failures > ---------------------------------------- > > Key: WFCORE-1525 > URL: https://issues.jboss.org/browse/WFCORE-1525 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 2.1.0.Final > Reporter: Dennis Reed > Assignee: Bartosz Spyrko-Śmietanko > Fix For: 3.0.0.Alpha1 > > > When ageout-history cannot delete the old CP files, it silently fails and returns "success". > LocalAgeoutHistoryHandler#recursiveDelete does keep track of whether the > delete failed or succeeded, but the return value from this method is ignored > in execute(...). > If recursiveDelete returns false, it should report a failure. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-706) PeerIdentityContext#getCurrentIdentity should not be final

by David Lloyd (JIRA)

David Lloyd created ELY-706: ------------------------------- Summary: PeerIdentityContext#getCurrentIdentity should not be final Key: ELY-706 URL: https://issues.jboss.org/browse/ELY-706 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd This method should be non-final so that subclasses can override the return type to something more specific. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

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

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7219?page=com.atlassian.jira.plugin.... ] Jan Kalina reopened WFLY-7219: ------------------------------ > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7436: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Some attributes in Elytron ldap-realm are nillable=false but have set default values > ------------------------------------------------------------------------------------ > > Key: WFLY-7436 > URL: https://issues.jboss.org/browse/WFLY-7436 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Optional > Labels: user_experience > > Following attributes Elytron ldap-realm are nillable=false but have set default values: > * {{identity-mapping.use-recursive-search}} > * {{identity-mapping.user-password-mapper.writable}} > * {{identity-mapping.user-password-mapper.verifiable}} > Using nillable=false with set default value can be confused (because default value should be used in case when none value is set and nillable=false says that any value must by used). > Suggestion: > Since none of these mentioned attributes is required by CLI commands set nillable for these attributes to true. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7437) Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7437?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7437: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm > ------------------------------------------------------------------------ > > Key: WFLY-7437 > URL: https://issues.jboss.org/browse/WFLY-7437 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Minor > Labels: user_experience > > Attribute {{identity-mapping.otp-credential-mapper}} from Elytron ldap-realm should include Object which should contain four required attributes - algorithm-from, hash-from, seed-from, sequence-from. All of these attributes are set as nillable=false. > However CLI allows to run command where otp-credential-mapper attribute is added without any attributes which is inconsistent with their nillable=false. See following command: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > {code} > Moreover, this command results to configuration xml without any otp-credential-mapper: > {code} > <ldap-realm name="ldap-realm" dir-context="ldap"> > <identity-mapping rdn-identifier="uid"/> > </ldap-realm> > {code} > In case when at least one of otp-credential-mapper required attribute is added, then CLI command correctly fails: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={algorithm-from=atr}}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: hash-from may not be null", > "rolled-back" => true > } > {code} > Suggestion: > Do not allow to add {{identity-mapping.otp-credential-mapper}} without required attributes. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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