December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1910) Develop JWT Token Issuer

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1910?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1910: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Develop JWT Token Issuer > ------------------------ > > Key: ELY-1910 > URL: https://issues.jboss.org/browse/ELY-1910 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Major > Fix For: 2.0.0.Alpha7 > > > Assigning to API / SPI for now but we may want to create a new component to track token based authentication, especially JWT. > It may be desirable for us to be able to issue JWT tokens that can be used elsewhere. > At the moment our identity propagation makes use of credentials delegated to us during authentication but we have some more opportunities if we can obtain new credentials dynamically for this propagation. > An ideal use case for this could be a traditional web application already secured using traditional authentication such as username / password via a form, in that case the application will have a resulting SecurityIdentity with attributes, roles, and permissions assigned. > This feature request is to consider a component internal to the process to convert the SecurityIdentity to a JWT token that can now be used for any outbound calls as the identity to propagate the identity. > One possibility is some kind of transformation that can be applied on the SecurityDomain so the resulting SecurityIdentity has an associated JWT token credential as soon as it is created. > Another alternative is more integration within authentication client, the destination could be taken into account so different tokens / mappings are applied for different destinations. > I wont create the separate Jira issue yet but this could also open an option to dynamically obtain a token from a remote issuer - we may have been delegated a credential we can use to authentication against a remote identity provider and request a token that way. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1888) Review Context Association

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1888?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1888: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Review Context Association > -------------------------- > > Key: ELY-1888 > URL: https://issues.jboss.org/browse/ELY-1888 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, MicroProfile > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 2.0.0.Alpha7 > > > Our APIs are very much written for objects to be associated with the current Thread and to remain associated either until they are replaced or the call stack returns to the point where association occurs and the association is automatically removed. > Concurrent APIs are always a problem in this area as a "request" can now traverse multiple Threads, issues arise in relation to propagation to worker threads but also potentially in the association for any resulting callbacks / resumption of work across different threads. > We should double check our relationship with Jakarta Concurrency: - > https://projects.eclipse.org/projects/ee4j.cu > The following specification within MicroProfile is looking into some mechanisms for this association: - > https://github.com/eclipse/microprofile-context-propagation > It may be preferable for our APIs to remain unchanged but instead we provide sufficient integration to capture our current context specific instances and propagate them. > As we have more than one item that can be associated we may want to review if we want to use a single context internally that associates multiple items so we only have one item to propagate. > Generally the items we associate are immutable so cross Thread modifications are not likely to be an issue. > Alternatively we may choose to revisit our association APIs. > Overall creating this issue for now as it is an area we will need to investigate further and plan for - tentatively scheduled against 2.0 although I suspect we will need to handle this within a 1.x release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1858) Create Three new shaded jars elytron-common, elytron-acme, and elytron-password

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1858?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1858: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Create Three new shaded jars elytron-common, elytron-acme, and elytron-password > ------------------------------------------------------------------------------- > > Key: ELY-1858 > URL: https://issues.jboss.org/browse/ELY-1858 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 2.0.0.Alpha7 > > > These are for use by Quarkus bundling together some of the common dependencies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1742) Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1742?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1742: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API > ---------------------------------------------------------------------------------------------------- > > Key: ELY-1742 > URL: https://issues.jboss.org/browse/ELY-1742 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1741) Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1741?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1741: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1741 > URL: https://issues.jboss.org/browse/ELY-1741 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-76) Release Elytron Web 2.0.0.Alpha3

by Farah Juma (Jira)

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

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-77) Upgrade WildFly Elytron to 2.0.0.Alpha6

by Farah Juma (Jira)

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

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-243) Ensure reference to repository is removed from pom

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-243?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-243: --------------------------- Fix Version/s: 1.11.0.CR4 (was: 1.11.0.CR3) > Ensure reference to repository is removed from pom > -------------------------------------------------- > > Key: ELY-243 > URL: https://issues.jboss.org/browse/ELY-243 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR4 > > > We need to ensure the reference to the JBoss repo is removed from the pom and artefacts are available from Maven Central. > Also at this point probably good to put the steps in place for Elytron to also be available from Maven Central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4677) [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4677?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4677: ------------------------------------------- [~dadossan] I believe that you are okay with the proposed mock, so I'm going to mark this as Resolved. And to follow-up on your point concerning indicating invalid drop targets - I found this guideline on the PF3 site: ??Hover over denied target: An icon should appear next to the cursor to signify an invalid drop target and the empty grey slot should remain at the original location where the item was selected.?? https://www.patternfly.org/v3/pattern-library/forms-and-controls/drag-and... If there's anything else that's needed, please let me know and feel free to reopen the jira. Thanks. [~karreiro] [~tirelli] ^^ > [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list > --------------------------------------------------------------------------------- > > Key: DROOLS-4677 > URL: https://issues.jboss.org/browse/DROOLS-4677 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: karreiro > Assignee: Elizabeth Clayton > Priority: Major > Labels: UXTeam, drools-tools, ux > Attachments: Read-only.png > > > The new drag and drop mechanism, added by the [Data Type UI enhancements|https://docs.google.com/presentation/u/1/d/10GZUd6oLaQohK27i...] does not specify how to handle read-only data types. > Scenarios: > - A User drags a regular data type to a position inside of read-only data type > - A User drags a read-only data type to a position inside of regular data type > _Notice: Read only data types appear when a DMN model has another DMN model included, and the external one has some data types._ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4677) [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4677?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-4677. --------------------------------------- Resolution: Done [~dadossan] reviewed. > [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list > --------------------------------------------------------------------------------- > > Key: DROOLS-4677 > URL: https://issues.jboss.org/browse/DROOLS-4677 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: karreiro > Assignee: Elizabeth Clayton > Priority: Major > Labels: UXTeam, drools-tools, ux > Attachments: Read-only.png > > > The new drag and drop mechanism, added by the [Data Type UI enhancements|https://docs.google.com/presentation/u/1/d/10GZUd6oLaQohK27i...] does not specify how to handle read-only data types. > Scenarios: > - A User drags a regular data type to a position inside of read-only data type > - A User drags a read-only data type to a position inside of regular data type > _Notice: Read only data types appear when a DMN model has another DMN model included, and the external one has some data types._ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019