May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2746) Move elytron management security tests from full to core

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2746?page=com.atlassian.jira.plugi... ] Ondrej Lukas commented on WFCORE-2746: -------------------------------------- [~luck3y] Do you plan to add some equivalent of Arquillian {{InSequence}} annotation to {{WildflyTestRunner}}? Is there any possibility how to simply run following flow in Test Case in WF Core TS: # setup server # run some tests # change some attribute in configuration which needs server reload -> reload server # run some tests # reset server configuration > Move elytron management security tests from full to core > -------------------------------------------------------- > > Key: WFCORE-2746 > URL: https://issues.jboss.org/browse/WFCORE-2746 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security, Test Suite > Reporter: Brian Stansberry > > Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. > Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 > There are a number of aspects to this, for which I'll create subtasks. > Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. > -org.jboss.as.test.integration.security.perimeter.* [2]- > -org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase- > -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- > org.jboss.as.test.integration.security.credentialreference [2] > integration/elytron/ > [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. > [2] Currently using Arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1914) S3_PING doesn't work with S3 buckets created in Frankfurt region

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1914?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1914: -------------------------------- I recently ported Zalando's NATVE_S3_PING to 4.0 and refactored it quite a bit. The port is at [1]. This is what I'd recommend if you're running on EC2. As mentioned elsewhere, I want to deprecate S3_PING as soon as I have a native discovery protocol for Google Cloud Platform [2]. [1] https://github.com/jgroups-extras [2] https://issues.jboss.org/browse/JGRP-2170 > S3_PING doesn't work with S3 buckets created in Frankfurt region > ----------------------------------------------------------------- > > Key: JGRP-1914 > URL: https://issues.jboss.org/browse/JGRP-1914 > Project: JGroups > Issue Type: Bug > Reporter: Gleb Leonov > Assignee: Bela Ban > Fix For: 4.1 > > Attachments: AWS4.png > > > I tried to use S3_PING with access and secret key pair. However, I got 400 (Bad Request) error. After some investigation, I found that modern S3 buckets created in Frankfurt needs amazon v4 authentication, which needs hmac-sha256. But now S3_PING supports only hmac-sha1, so I see no way to use S3_PING with buckets in Frankfurt region. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2109 at 5/11/17 7:29 AM: --------------------------------------------------------- Yes: https://issues.jboss.org/browse/JGRP-2170. Are you interested? :-) was (Author: belaban): Yes: https://issues.jboss.org/browse/JGRP-2170 > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2109 at 5/11/17 7:28 AM: --------------------------------------------------------- Sorry, I cannot deprecate S3_PING, at least for the time being, as GOOGLE_PING depends on it. Until I haven't re-implemented GOOGLE_PING with an implementation that uses the GCP SDK, I have to rely on S3_PING. was (Author: belaban): Sorry, I cannot deprecate S3_PING, at least for the time being, as GOOGEL_PING depends on it. Until I haven't re-implemented GOOGLE_PING with an implementation that uses the GCP SDK, I have to rely on S3_PING. > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2109: -------------------------------- Yes: https://issues.jboss.org/browse/JGRP-2170 > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2170) GOOGLE_PING2

by Bela Ban (JIRA)

Bela Ban created JGRP-2170: ------------------------------ Summary: GOOGLE_PING2 Key: JGRP-2170 URL: https://issues.jboss.org/browse/JGRP-2170 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1 New version of GOOGLE_PING based on the official Google Cloud Storage APIs [1]. The existing GOOGLE_PING protocol extends S3_PING which I want to deprecate, so creating GOOGLE_PING2 is a prerequisite to that. Hosting will be at jgroups-extras. [1] https://cloud.google.com/storage/docs/apis -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on JGRP-2109: -------------------------------------- Is there a jira for native google ping, i.e. using the official client? > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2670) list-add doesn't work for nested list of child attribute

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2670?page=com.atlassian.jira.plugi... ] Harald Pehl edited comment on WFCORE-2670 at 5/11/17 7:03 AM: -------------------------------------------------------------- [~brian.stansberry] can you give a rough estimate when this will be fixed. There's a HAL issue depending on this issue: JBEAP-10238. If we want to get it into the next DR release we need some time ahead to apply the fix to HAL. > list-add doesn't work for nested list of child attribute > -------------------------------------------------------- > > Key: WFCORE-2670 > URL: https://issues.jboss.org/browse/WFCORE-2670 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > Priority: Critical > > The list-add doesn't work for a child of an attribute as in the example below > Add a dir-context first > {code} > /profile=full/subsystem=elytron/dir-context=dir2:add(url="ldap://test") > {code} > Add a ldap-realm > {code} > /profile=full/subsystem=elytron/ldap-realm=foobar2:add(dir-context=dir2,identity-mapping={rdn-identifier=test}) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => {"main-server-group" => {"host" => {"master" => {"server-one" => {"response" => { > "outcome" => "success", > "response-headers" => {"process-state" => "reload-required"} > }}}}}} > } > {code} > This is the command to add the item to the list > {code} > /profile=full/subsystem=elytron/ldap-realm=foobar2:list-add(name=identity-mapping.new-identity-attributes,value={name=key2,value=["val1","val2"]}) > { > "outcome" => "failed", > "result" => undefined, > "server-groups" => undefined, > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2109: -------------------------------- Sorry, I cannot deprecate S3_PING, at least for the time being, as GOOGEL_PING depends on it. Until I haven't re-implemented GOOGLE_PING with an implementation that uses the GCP SDK, I have to rely on S3_PING. > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1914) S3_PING doesn't work with S3 buckets created in Frankfurt region

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1914?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1914: -------------------------------- I think I'm going to deprecate S3_PING as discussed in [1], as there are far better alternatives, rendering this issue moot. Thoughts? [1] https://issues.jboss.org/browse/JGRP-2109 > S3_PING doesn't work with S3 buckets created in Frankfurt region > ----------------------------------------------------------------- > > Key: JGRP-1914 > URL: https://issues.jboss.org/browse/JGRP-1914 > Project: JGroups > Issue Type: Bug > Reporter: Gleb Leonov > Assignee: Bela Ban > Fix For: 4.1 > > Attachments: AWS4.png > > > I tried to use S3_PING with access and secret key pair. However, I got 400 (Bad Request) error. After some investigation, I found that modern S3 buckets created in Frankfurt needs amazon v4 authentication, which needs hmac-sha256. But now S3_PING supports only hmac-sha1, so I see no way to use S3_PING with buckets in Frankfurt region. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 May 2017