April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1466) Add configuration option to BASIC mechanism to switch off challenging

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1466?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1466: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.3.0.Final) > Add configuration option to BASIC mechanism to switch off challenging > --------------------------------------------------------------------- > > Key: ELY-1466 > URL: https://issues.jboss.org/browse/ELY-1466 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.3.1.Final > > > This may be desirable where paired with FORM auth so users can use FORM auth and other clients use BASIC. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1464) Programatic authentication should be caching the SecurityIdentity not the name of the identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1464?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1464: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.3.0.Final) > Programatic authentication should be caching the SecurityIdentity not the name of the identity > ---------------------------------------------------------------------------------------------- > > Key: ELY-1464 > URL: https://issues.jboss.org/browse/ELY-1464 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.3.1.Final > > > By only caching the name of the identity the server authentication context -> security domain -> security realm chain is called for each subsequent request when we should have been able to re-use an existing identity. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1504) Support Elytron specific callbacks with JASPIC ServerAuthenticationModules

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1504?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1504: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.3.0.Final) > Support Elytron specific callbacks with JASPIC ServerAuthenticationModules > -------------------------------------------------------------------------- > > Key: ELY-1504 > URL: https://issues.jboss.org/browse/ELY-1504 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.3.1.Final > > > JASPIC already supports the use of a CallbackHandler for communication between the ServerAuthenticationModule and the container the first stage of implementation is to support the callbacks mandated by the spec - this task is to follow up and add support for Elytron specific callbacks. > The reason to split this out is we may still want to handle our core lifecycle related callbacks so of the remaining callbacks we will need to decide which ones we want to support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1566) Release WildFly Elytron 1.3.0.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1566?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1566. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.3.0.Final > ----------------------------------- > > Key: ELY-1566 > URL: https://issues.jboss.org/browse/ELY-1566 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3764) Upgrade WildFly Elytron to 1.3.0.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3764?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3764: ------------------------------------- Fix Version/s: 5.0.0.Alpha4 > Upgrade WildFly Elytron to 1.3.0.Final > -------------------------------------- > > Key: WFCORE-3764 > URL: https://issues.jboss.org/browse/WFCORE-3764 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 5.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3764) Upgrade WildFly Elytron to 1.3.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3764: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.3.0.Final Key: WFCORE-3764 URL: https://issues.jboss.org/browse/WFCORE-3764 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1566) Release WildFly Elytron 1.3.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1566: ------------------------------------- Summary: Release WildFly Elytron 1.3.0.Final Key: ELY-1566 URL: https://issues.jboss.org/browse/ELY-1566 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.3.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2264) JGRP000012 with SAP Hybris default config

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2264?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2264 at 4/24/18 11:50 AM: ---------------------------------------------------------- This is because {{mcast_addr}} and {{mcast_port}} in {{UDP}} are the same for both the {{dev-hybris-broadcast}} and {{con-hybris-broadcast}} clusters. Pick different values for one or both of these attributes, and the warnings will disappear. was (Author: belaban): This is because {{mcast_addr}} and {{mcast_port}} in {{UDP}} are the same for both the {{dev-hybris-broadcast}} and {{con-hybris-broadcast}} clusters. > JGRP000012 with SAP Hybris default config > ----------------------------------------- > > Key: JGRP-2264 > URL: https://issues.jboss.org/browse/JGRP-2264 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Diana Haase > Assignee: Bela Ban > > A lot of discarted messages in console.log of Hybris Clusters > [UDP] | JGRP000012: discarded message from different cluster ... > [UDP] | JGRP000012: discarded message from different cluster dev-hybris-broadcast (our cluster is con-hybris-broadcast). Sender was xxxxx (received 724 identical messages from xxxx in the last 60347 ms) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2264) JGRP000012 with SAP Hybris default config

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2264?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2264. ---------------------------- Resolution: Rejected > JGRP000012 with SAP Hybris default config > ----------------------------------------- > > Key: JGRP-2264 > URL: https://issues.jboss.org/browse/JGRP-2264 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Diana Haase > Assignee: Bela Ban > > A lot of discarted messages in console.log of Hybris Clusters > [UDP] | JGRP000012: discarded message from different cluster ... > [UDP] | JGRP000012: discarded message from different cluster dev-hybris-broadcast (our cluster is con-hybris-broadcast). Sender was xxxxx (received 724 identical messages from xxxx in the last 60347 ms) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2264) JGRP000012 with SAP Hybris default config

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2264?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2264 at 4/24/18 11:41 AM: ---------------------------------------------------------- This is because {{mcast_addr}} and {{mcast_port}} in {{UDP}} are the same for both the {{dev-hybris-broadcast}} and {{con-hybris-broadcast}} clusters. was (Author: belaban): This is because {{mcast_addr}} and {{mcast_port}} in {{UDP}} are the same for both the {{dev-hybris-broadcast }} and {{con-hybris-broadcast}} clusters. > JGRP000012 with SAP Hybris default config > ----------------------------------------- > > Key: JGRP-2264 > URL: https://issues.jboss.org/browse/JGRP-2264 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Diana Haase > Assignee: Bela Ban > > A lot of discarted messages in console.log of Hybris Clusters > [UDP] | JGRP000012: discarded message from different cluster ... > [UDP] | JGRP000012: discarded message from different cluster dev-hybris-broadcast (our cluster is con-hybris-broadcast). Sender was xxxxx (received 724 identical messages from xxxx in the last 60347 ms) -- 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 April 2018