October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-64) Bring the dependency versions in-line with WildFly Core

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-64?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-64: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Bring the dependency versions in-line with WildFly Core > ------------------------------------------------------- > > Key: ELYWEB-64 > URL: https://issues.jboss.org/browse/ELYWEB-64 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha2, 1.6.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-57) Update WildFly Checkstyle Config to 1.0.8.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-57?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-57: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Update WildFly Checkstyle Config to 1.0.8.Final > ----------------------------------------------- > > Key: ELYWEB-57 > URL: https://issues.jboss.org/browse/ELYWEB-57 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.5.0.Final, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-56) Upgrade JBoss Parent to version 35

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-56?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-56: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Upgrade JBoss Parent to version 35 > ---------------------------------- > > Key: ELYWEB-56 > URL: https://issues.jboss.org/browse/ELYWEB-56 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.5.0.Final, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-45) Bring the dependency versions in-line with WildFly Core

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-45?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-45: ----------------------------- Fix Version/s: (was: 2.0.0.Alpha2) > Bring the dependency versions in-line with WildFly Core > ------------------------------------------------------- > > Key: ELYWEB-45 > URL: https://issues.jboss.org/browse/ELYWEB-45 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.4.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-51) Update ElytronHttpExchange.getSSLSession() to use Undertows SSLSessionInfo

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-51?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-51: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Update ElytronHttpExchange.getSSLSession() to use Undertows SSLSessionInfo > -------------------------------------------------------------------------- > > Key: ELYWEB-51 > URL: https://issues.jboss.org/browse/ELYWEB-51 > Project: Elytron Web > Issue Type: Task > Components: Undertow > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.5.0.CR2, 2.0.0.Alpha2 > > > This is an opportunity for this method to be compatible with both Undertow 2 and 3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-50) Add test case testing use of AuthenticationManager

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-50?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-50: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Add test case testing use of AuthenticationManager > -------------------------------------------------- > > Key: ELYWEB-50 > URL: https://issues.jboss.org/browse/ELYWEB-50 > Project: Elytron Web > Issue Type: Bug > Components: Undertow Servlet > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.5.0.CR2, 2.0.0.Alpha2 > > > This should likely just create an Undertow deployment programatically and enable HTTP BASIC authentication similar to the non servlet case but now using the servlet level integration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-45) Bring the dependency versions in-line with WildFly Core

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-45?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-45: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Bring the dependency versions in-line with WildFly Core > ------------------------------------------------------- > > Key: ELYWEB-45 > URL: https://issues.jboss.org/browse/ELYWEB-45 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.4.0.Final, 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-46) Elytron Bearer Token Authentication - Return a 401 on Invalid Token test fix

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-46?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-46: ----------------------------- Fix Version/s: 2.0.0.Alpha2 > Elytron Bearer Token Authentication - Return a 401 on Invalid Token test fix > ---------------------------------------------------------------------------- > > Key: ELYWEB-46 > URL: https://issues.jboss.org/browse/ELYWEB-46 > Project: Elytron Web > Issue Type: Bug > Reporter: Martin Mazanek > Assignee: Martin Mazanek > Priority: Major > Fix For: 1.4.0.Final, 2.0.0.Alpha2 > > > *Issue* > Currently, Elytron will send back a 403 Response when an invalid bearer token is sent. For the built-in JWT validator (the token validation we are using), this [includes a few checks like signature, expiration time, audience and issuer|https://github.com/wildfly-security/wildfly-elytron/blob/1.7.0.CR1...]. > It seems that the current [BearerTokenAuthenticationMechanism|https://github.com/wildfly-security/wi...] does not differentiate between failed authentication and failed authorization, returning a 403 in both cases. This produces conflicting and erroneous results. Did I fail to authenticate (say, expired JWT) or did I authenticate but do not have access to the resource in question? > This would also be closer in line with [RFC 6750 (The OAuth 2.0 Authorization Framework: Bearer Token Usage)|https://tools.ietf.org/html/rfc6750#section-3] which includes an example of an expired (invalid) token. > {quote} > And in response to a protected resource request with an > authentication attempt using an expired access token: > HTTP/1.1 401 Unauthorized > WWW-Authenticate: Bearer realm="example", > error="invalid_token", > error_description="The access token expired" > {quote} > *Potential Solution* > Perhaps this could be ameliorated by something akin to the following change in BearerTokenAuthenticationMechanism::evaluateRequest by differentiating between failure to authorize and failure to authenticate the token. Merely a quick, unvetted example as I haven't had enough time to dig in to the source. > {code} > if (verifyCallback.isVerified()) { > AuthorizeCallback authorizeCallback = new AuthorizeCallback(null, null); > handleCallback(authorizeCallback); > if (authorizeCallback.isAuthorized()) { > httpBearer.debugf("Token authentication successful."); > handleCallback(new IdentityCredentialCallback(new BearerTokenCredential(tokenEvidence.getToken()), true)); > handleCallback(AuthenticationCompleteCallback.SUCCEEDED); > request.authenticationComplete(); > return; > } > else{ > httpBearer.debugf("Token authorization failed message."); > request.authenticationFailed("Some token unauthorized message", response -> response.setStatusCode(FORBIDDEN)); > return; > } > } > httpBearer.debugf("Token authentication failed."); > request.authenticationFailed("Invalid bearer token", response -> response.setStatusCode(UNAUTHORIZED)); > return; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-71) Upgrade WildFly Elytron to 2.0.0.Alpha5

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-71?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELYWEB-71. ------------------------------ Resolution: Done > Upgrade WildFly Elytron to 2.0.0.Alpha5 > --------------------------------------- > > Key: ELYWEB-71 > URL: https://issues.jboss.org/browse/ELYWEB-71 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-72) Release Elytron Web 2.0.0.Alpha2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-72?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELYWEB-72. ------------------------------ Resolution: Done > Release Elytron Web 2.0.0.Alpha2 > -------------------------------- > > Key: ELYWEB-72 > URL: https://issues.jboss.org/browse/ELYWEB-72 > Project: Elytron Web > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019