[JBoss JIRA] (WFLY-12574) Documentation for SSH authentication for Git persistence
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/WFLY-12574?page=com.atlassian.jira.plugin... ]
Ashley Abdel-Sayed updated WFLY-12574:
--------------------------------------
Summary: Documentation for SSH authentication for Git persistence (was: Support SSH authentication for Git persistence)
> Documentation for SSH authentication for Git persistence
> --------------------------------------------------------
>
> Key: WFLY-12574
> URL: https://issues.jboss.org/browse/WFLY-12574
> Project: WildFly
> Issue Type: Feature Request
> Components: Management, Security
> Reporter: Ashley Abdel-Sayed
> Assignee: Ashley Abdel-Sayed
> Priority: Major
> Labels: EAP-CD19
> Fix For: 11.0.0.Beta1
>
>
> Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4715) [DMN Designer] Structure is lost when user doesn't drag it enough
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4715?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-4715:
------------------------------------
Story Points: 2 (was: 3)
> [DMN Designer] Structure is lost when user doesn't drag it enough
> -----------------------------------------------------------------
>
> Key: DROOLS-4715
> URL: https://issues.jboss.org/browse/DROOLS-4715
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.30.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-not-enough.webm
>
>
> This issue is caused by DROOLS-4484
> If user drag a structure not enough == no reordering/reorganization caused by that drag, the structure is lost. See the attached video.
> ---
> ⚠️ Notice: this issue is caused by the absence of reference, like the the scenario mentioned on DROOLS-4710. This JIRA must be marked as resolved only when both scenarios are solved.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4715) [DMN Designer] Structure is lost when user doesn't drag it enough
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4715?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-4715:
------------------------------------
Story Points: 3
Sprint: 2019 Week 44-46 (from Okt 28)
> [DMN Designer] Structure is lost when user doesn't drag it enough
> -----------------------------------------------------------------
>
> Key: DROOLS-4715
> URL: https://issues.jboss.org/browse/DROOLS-4715
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.30.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-not-enough.webm
>
>
> This issue is caused by DROOLS-4484
> If user drag a structure not enough == no reordering/reorganization caused by that drag, the structure is lost. See the attached video.
> ---
> ⚠️ Notice: this issue is caused by the absence of reference, like the the scenario mentioned on DROOLS-4710. This JIRA must be marked as resolved only when both scenarios are solved.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (ELY-1440) FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself.
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/ELY-1440?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1440:
----------------------------------
Fix Version/s: 1.11.0.CR2
(was: 1.10.4.Final)
> FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself.
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1440
> URL: https://issues.jboss.org/browse/ELY-1440
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: API / SPI
> Reporter: Darran Lofthouse
> Priority: Major
> Fix For: 1.11.0.CR2
>
>
> This API was introduced to cover the case where authentication happens late in a request, generally that is quite a rare event.
> Even though the API may be popular it would likely happen once for a session and all future requests for that session the identity would be known in advance.
> At the moment by not running as the existing identity we are loosing all automatic identity outflow opportunities as calls pass from the servlet container to the EJB container.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months