September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-437) Maistra with Minimal Resource and Minimal Resource with Kiali

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-437: --------------------------------------------- Summary: Maistra with Minimal Resource and Minimal Resource with Kiali Key: SWSQE-437 URL: https://issues.jboss.org/browse/SWSQE-437 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley Minimal resource won't install kiali. Minimal resource file with Kiali look like: {code:yaml} apiVersion: "istio.openshift.com/v1alpha1" kind: "Installation" metadata: name: "istio-installation" spec: kiali: username: ${OPENSHIFT_KIALI_USERNAME} password: ${OPENSHIFT_KIALI_PASSWORD} {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-437) Maistra with Minimal Resource and Minimal Resource with Kiali

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-437?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-437: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Maistra with Minimal Resource and Minimal Resource with Kiali > ------------------------------------------------------------- > > Key: SWSQE-437 > URL: https://issues.jboss.org/browse/SWSQE-437 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Minimal resource won't install kiali. > Minimal resource file with Kiali look like: > {code:yaml} > apiVersion: "istio.openshift.com/v1alpha1" > kind: "Installation" > metadata: > name: "istio-installation" > spec: > kiali: > username: ${OPENSHIFT_KIALI_USERNAME} > password: ${OPENSHIFT_KIALI_PASSWORD} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-436) Kiali Checker needs to support both http and https

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-436: ---------------------------------- Summary: Kiali Checker needs to support both http and https Key: SWSQE-436 URL: https://issues.jboss.org/browse/SWSQE-436 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Matt Mahoney -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1677) Elytron Bearer Token Authentication - Return a 401 on Invalid Token

by Edward Stathopoulos (JIRA)

Edward Stathopoulos created ELY-1677: ---------------------------------------- Summary: Elytron Bearer Token Authentication - Return a 401 on Invalid Token Key: ELY-1677 URL: https://issues.jboss.org/browse/ELY-1677 Project: WildFly Elytron Issue Type: Feature Request Components: Authentication Mechanisms Affects Versions: 1.7.0.CR1 Reporter: Edward Stathopoulos *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.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-435) Fix failing UI automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-435?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-435: -------------------------------------- WIP https://github.com/Kiali-QE/kiali-qe-python/pull/79 > Fix failing UI automation tests > ------------------------------- > > Key: SWSQE-435 > URL: https://issues.jboss.org/browse/SWSQE-435 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/python-ui-tests-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3031: -------------------------------- Sprint: 2018 Week 45-47 > [DMN Designer] UX for Expand / Collapse all > ------------------------------------------- > > Key: DROOLS-3031 > URL: https://issues.jboss.org/browse/DROOLS-3031 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > > User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog. > h2. Manual acceptance test > - Expand > -- All collapsed initially > -- Something collapsed initially, something expanded already > -- All expanded already > - Collapse > -- All expanded initially > -- Something expanded initially, something collapsed already > -- All collapsed already > - No error warning in browser console log -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3031: -------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 45-47) > [DMN Designer] UX for Expand / Collapse all > ------------------------------------------- > > Key: DROOLS-3031 > URL: https://issues.jboss.org/browse/DROOLS-3031 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > > User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog. > h2. Manual acceptance test > - Expand > -- All collapsed initially > -- Something collapsed initially, something expanded already > -- All expanded already > - Collapse > -- All expanded initially > -- Something expanded initially, something collapsed already > -- All collapsed already > - No error warning in browser console log -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3031: -------------------------------- Story Points: 2 > [DMN Designer] UX for Expand / Collapse all > ------------------------------------------- > > Key: DROOLS-3031 > URL: https://issues.jboss.org/browse/DROOLS-3031 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > > User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog. > h2. Manual acceptance test > - Expand > -- All collapsed initially > -- Something collapsed initially, something expanded already > -- All expanded already > - Collapse > -- All expanded initially > -- Something expanded initially, something collapsed already > -- All collapsed already > - No error warning in browser console log -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3032: -------------------------------- Sprint: 2018 Week 42-44 > [DMN Designer] UX "empty" state for custom data types > ----------------------------------------------------- > > Key: DROOLS-3032 > URL: https://issues.jboss.org/browse/DROOLS-3032 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ] Liz Clayton reassigned DROOLS-3032: ----------------------------------- Assignee: Liz Clayton (was: Michael Anstis) > [DMN Designer] UX "empty" state for custom data types > ----------------------------------------------------- > > Key: DROOLS-3032 > URL: https://issues.jboss.org/browse/DROOLS-3032 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 September 2018