December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose information on authentication in use

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3443: ----------------------------------------- Summary: CLI ConnectionInfo should expose information on authentication in use (was: CLI ConnectionInfo should expose security realm.) > CLI ConnectionInfo should expose information on authentication in use > --------------------------------------------------------------------- > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3443: ---------------------------------------------- I understand, getting a description (open, unspecified) of the kind of authentication in place for the current connection would be enough for a CLI user. > CLI ConnectionInfo should expose security realm. > ------------------------------------------------ > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-1458) SelfSignedX509CertificateAndSigningKeyTest.testSelfSignedCertificateWithStringExtensionValues fails on IBM JDK

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1458?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on ELY-1458: --------------------------------- [~mchoma] Thanks for catching this. The Authority Information Access extension's OCSP URI must have both a scheme and a scheme-specific part (as mentioned in the GeneralName definition in RFC 3280). However, the test was erroneously specifying just "ocsp:uri:10.20.30.40:8080". Since the scheme was missing, IBM JDK was considering this extension to be invalid when attempting to parse it. I've submitted the following PR to fix the test and also ensure that we check the URI name is valid when attempting to create a GeneralName.URIName: https://github.com/wildfly-security/wildfly-elytron/pull/1043 > SelfSignedX509CertificateAndSigningKeyTest.testSelfSignedCertificateWithStringExtensionValues fails on IBM JDK > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-1458 > URL: https://issues.jboss.org/browse/ELY-1458 > Project: WildFly Elytron > Issue Type: Bug > Components: Certificate Authority > Affects Versions: 1.2.0.Beta10 > Reporter: Martin Choma > Assignee: Farah Juma > > With IBM java > {noformat} > java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr4fp6-20170518_02(SR4 FP6)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20170516_348050 (JIT enabled, AOT enabled) > J9VM - R28_20170516_1905_B348050 > JIT - tr.r14.java_20170516_348050 > GC - R28_20170516_1905_B348050_CMPRSS > J9CL - 20170516_348050) > JCL - 20170516_01 based on Oracle jdk8u131-b11 > {noformat} > run test > {noformat} > mvn test -Dtest=SelfSignedX509CertificateAndSigningKeyTest > [INFO] Running org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKeyTest > [ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.372 s <<< FAILURE! - in org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKeyTest > [ERROR] testSelfSignedCertificateWithStringExtensionValues(org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKeyTest) Time elapsed: 0.274 s <<< FAILURE! > java.lang.AssertionError > at org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKeyTest.testSelfSignedCertificateWithStringExtensionValues(SelfSignedX509CertificateAndSigningKeyTest.java:197) > {noformat} > This is test line failing > {code:java|title=SelfSignedX509CertificateAndSigningKeyTest.java} > byte[] authorityInfoAccessExtension = certificate.getExtensionValue(X500.OID_PE_AUTHORITY_INFO_ACCESS); > assertNotNull(authorityInfoAccessExtension); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-3443: ------------------------------------------ Until we know what we really want to expose I don't think we should be adding anything else - the names are arbitrary internal names. Even the notion of a realm name is now something really specific to a specific authentication mechanism. > CLI ConnectionInfo should expose security realm. > ------------------------------------------------ > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9592) Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods

by Marcus Handte (JIRA)

[ https://issues.jboss.org/browse/WFLY-9592?page=com.atlassian.jira.plugin.... ] Marcus Handte commented on WFLY-9592: ------------------------------------- What's the point in asking me to file another bug, if it is closed immediately as outdated? Nevermind. > Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods > --------------------------------------------------------------------------------- > > Key: WFLY-9592 > URL: https://issues.jboss.org/browse/WFLY-9592 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final > Environment: Wildfly 10.1.0.Final in an Arquillian Managed Container Test > Reporter: Marcus Handte > Priority: Minor > > EJB methods with array parameters are causing EJBAccessExceptions when they are annotated with @PermitAll. This bug seemed to be present in 8.0.0.Alpha2 and was fixed (see WFLY-1658). But it seems to be present again in 10.1.0.Final. > For my own use case, this is not a problem since I can simply change the method signatures to use lists instead of arrays. However, I can imagine that this could be a more significant problem for people trying to run existing code that they do not want to (or cannot) touch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3443: ---------------------------------------------- The use case is that once you are connected you can't retrieve the source of authentication. You are user X but don't know from which realm it comes from, today you have to query the model and see that the interface you are connected to references a sasl-factory with digest + realm-name. A synthetic information would help specialy when making SASL auth configuration changes from CLI. > CLI ConnectionInfo should expose security realm. > ------------------------------------------------ > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9593) Add clustering externalizers for InetAddress and InetSocketAddress

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9593: ---------------------------------- Summary: Add clustering externalizers for InetAddress and InetSocketAddress Key: WFLY-9593 URL: https://issues.jboss.org/browse/WFLY-9593 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro InetAddress can be marshalled as a fixed sized array depending on whether the address is IPv4 or IPv6, which can be determined by the implementation class. InetSocketAddress can marshal its address using the InetAddress externalizer, and its port as an unsigned short. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-3443: ------------------------------------------ No Elytron realms only have a name to give us something to reference in a model, sharing this information with an end user would also not make sense. > CLI ConnectionInfo should expose security realm. > ------------------------------------------------ > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3443: ---------------------------------------------- [~dlofthouse], right, If I authenticate using sasl-factory, no realm displayed. Is there a way to retrieve the elytron realm name in this case? > CLI ConnectionInfo should expose security realm. > ------------------------------------------------ > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-204) Create best practices document for writing automation on mojo

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-204?page=com.atlassian.jira.pl... ] Filip Brychta commented on HAWKULARQE-204: ------------------------------------------ Created document https://mojo.redhat.com/docs/DOC-1157376 > Create best practices document for writing automation on mojo > ------------------------------------------------------------- > > Key: HAWKULARQE-204 > URL: https://issues.jboss.org/browse/HAWKULARQE-204 > Project: Hawkular QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > * create the document > * share it with the team -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

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 December 2017