June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10519) remove Hibernate JPA 2.1 + Hibernate ORM 5.1.x + Hibernate Search 5.5.8.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10519?page=com.atlassian.jira.plugin... ] Scott Marlow reassigned WFLY-10519: ----------------------------------- Assignee: Scott Marlow (was: Jason Greene) > remove Hibernate JPA 2.1 + Hibernate ORM 5.1.x + Hibernate Search 5.5.8.Final > ----------------------------------------------------------------------------- > > Key: WFLY-10519 > URL: https://issues.jboss.org/browse/WFLY-10519 > Project: WildFly > Issue Type: Task > Reporter: Scott Marlow > Assignee: Scott Marlow > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10519) remove Hibernate JPA 2.1 + Hibernate ORM 5.1.x + Hibernate Search 5.5.8.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10519?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10519: -------------------------------- Component/s: JPA / Hibernate > remove Hibernate JPA 2.1 + Hibernate ORM 5.1.x + Hibernate Search 5.5.8.Final > ----------------------------------------------------------------------------- > > Key: WFLY-10519 > URL: https://issues.jboss.org/browse/WFLY-10519 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-211) Create Prototype Jenkins Istio Job - Post Message

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-211?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-211: ------------------------------- Reporter: Tiago Moreira Vieira (was: Tiago Vilas Boas) > Create Prototype Jenkins Istio Job - Post Message > ------------------------------------------------- > > Key: SWSQE-211 > URL: https://issues.jboss.org/browse/SWSQE-211 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Tiago Moreira Vieira > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-211) Create Prototype Jenkins Istio Job - Post Message

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-211?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-211: ------------------------------- Reporter: Tiago Vilas Boas (was: Matt Mahoney) > Create Prototype Jenkins Istio Job - Post Message > ------------------------------------------------- > > Key: SWSQE-211 > URL: https://issues.jboss.org/browse/SWSQE-211 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Tiago Vilas Boas > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2532: ------------------------------------- [~jomarko] While I like it as well, I removed the cell highlighting because I got feedback that probably isn't in scope at the moment. - I was playing around with some ideas and added a pdf with an alternative design as well. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: Alternative.pdf, RoundF2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: Alternative.pdf > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: Alternative.pdf, RoundF2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: (was: roundE-scaled.pdf) > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: RoundF2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: (was: RoundF.pdf) > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: RoundF2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2586) CSS/HTML for scenario simulation UX

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2586?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2586: ------------------------------------- [~srambach] [~danielezonca] I ran the dialog by [~manstis], and he says it's do-able. There's already some pop-overs in the demo with controls inside. He would probably be the best person to followup with, for additional questions/concerns. > CSS/HTML for scenario simulation UX > ----------------------------------- > > Key: DROOLS-2586 > URL: https://issues.jboss.org/browse/DROOLS-2586 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: UX, UXTeam > Attachments: Screen Shot 2018-06-05 at 3.44.15 PM.png > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide CSS/HTML to support wireframe designs which includes the following: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1597) Identity Restoration where the Principal is not quite enough.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1597: ------------------------------------- Summary: Identity Restoration where the Principal is not quite enough. Key: ELY-1597 URL: https://issues.jboss.org/browse/ELY-1597 Project: WildFly Elytron Issue Type: Enhancement Components: Realms Reporter: Darran Lofthouse Priority: Critical Fix For: 1.4.0.CR1 Presently our authentication process is build around a SecurityRealm being able to create a RealmIdentity which we then convert to an AuthorizationIdentity which is then converted to a SecurityIdentity after applying appropriate SecurityDomain configured mappings. Generally in a SecurityRealm one of two different methods tend to be used to create the RealmIdentity. {code:java} RealmIdentity getRealmIdentity(Principal principal) throws RealmUnavailableException {code} or {code:java} RealmIdentity getRealmIdentity(Evidence evidence) throws RealmUnavailableException {code} Generally from the realms we know about, where the Principal form of the method is used the realm will likely load the attributes that go into the AuthorizationIdentity from another source, however for the form that takes Evidence often the attributes can be derived from the evidence. Where we persist identities to be restored later such as identity propagation, batch, clustering etc we persist the name of the identity and use it to restore the identity using the Principal form of the above methods. For cases where an identity was originally created using evidence we no longer have sufficient information to recreate the identity. This Enhancement is to review how we can address this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

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