October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12661) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

Farah Juma created WFLY-12661: --------------------------------- Summary: Make IP address of remote EJB client accessible to the developer from within app authentication code Key: WFLY-12661 URL: https://issues.jboss.org/browse/WFLY-12661 Project: WildFly Issue Type: Feature Request Components: Security Reporter: Farah Juma Assignee: Farah Juma When a user writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12660) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12660?page=com.atlassian.jira.plugin... ] Farah Juma deleted WFLY-12660: ------------------------------ > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12660 > URL: https://issues.jboss.org/browse/WFLY-12660 > Project: WildFly > Issue Type: Feature Request > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Minor > > This requirement now applies to the new security implementation based on Elytron. > When a user writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12660) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12660?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12660: ------------------------------ Labels: (was: EAP-CD19 Previous_RFE eap-7.2.0-deferred eap-7.3.0-deferred) > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12660 > URL: https://issues.jboss.org/browse/WFLY-12660 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Minor > > This requirement now applies to the new security implementation based on Elytron. > When a user writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12660) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12660?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12660: ------------------------------ Description: This requirement now applies to the new security implementation based on Elytron. When a user writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. was: This requirement now applies to the new security implementation based on Elytron. When a customer writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. ==================== 2. Who is the customer behind the request? Account: Alcatel - Canada (612917) TAM customer: no SRM customer: no Strategic: no 3. What is the nature and description of the request? The customer wants to be able to get the IP address of the EJB client in the login module when the security-realm is configured to defer to jaas. 4. Why does the customer need this? (List the business requirements here) The customer needs the IP address of the client during the authentication process. They use the IP address in their custom login module. 5. How would the customer like to achieve this? (List the functional requirements here) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Configure the ApplicationRealm security-realm to defer to JAAS. Implement a custom login module that retrieves the IP address of the standalone EJB client. 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as possible. > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12660 > URL: https://issues.jboss.org/browse/WFLY-12660 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Minor > Labels: EAP-CD19, Previous_RFE, eap-7.2.0-deferred, eap-7.3.0-deferred > > This requirement now applies to the new security implementation based on Elytron. > When a user writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12660) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12660?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12660: ------------------------------ Description: This requirement now applies to the new security implementation based on Elytron. When a customer writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. ==================== 2. Who is the customer behind the request? Account: Alcatel - Canada (612917) TAM customer: no SRM customer: no Strategic: no 3. What is the nature and description of the request? The customer wants to be able to get the IP address of the EJB client in the login module when the security-realm is configured to defer to jaas. 4. Why does the customer need this? (List the business requirements here) The customer needs the IP address of the client during the authentication process. They use the IP address in their custom login module. 5. How would the customer like to achieve this? (List the functional requirements here) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Configure the ApplicationRealm security-realm to defer to JAAS. Implement a custom login module that retrieves the IP address of the standalone EJB client. 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as possible. was: UPDATE: This requirement now applies to the new security implementation based on Elytron. When a customer writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. ==================== 2. Who is the customer behind the request? Account: Alcatel - Canada (612917) TAM customer: no SRM customer: no Strategic: no 3. What is the nature and description of the request? The customer wants to be able to get the IP address of the EJB client in the login module when the security-realm is configured to defer to jaas. 4. Why does the customer need this? (List the business requirements here) The customer needs the IP address of the client during the authentication process. They use the IP address in their custom login module. 5. How would the customer like to achieve this? (List the functional requirements here) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Configure the ApplicationRealm security-realm to defer to JAAS. Implement a custom login module that retrieves the IP address of the standalone EJB client. 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as possible. > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12660 > URL: https://issues.jboss.org/browse/WFLY-12660 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Minor > Labels: EAP-CD19, Previous_RFE, eap-7.2.0-deferred, eap-7.3.0-deferred > > This requirement now applies to the new security implementation based on Elytron. > When a customer writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. > ==================== > 2. Who is the customer behind the request? > Account: Alcatel - Canada (612917) > TAM customer: no > SRM customer: no > Strategic: no > 3. What is the nature and description of the request? > The customer wants to be able to get the IP address of the > EJB client in the login module when the security-realm is > configured to defer to jaas. > 4. Why does the customer need this? (List the business requirements here) > The customer needs the IP address of the client during the authentication process. > They use the IP address in their custom login module. > 5. How would the customer like to achieve this? (List the functional requirements here) > 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. > Configure the ApplicationRealm security-realm to defer to JAAS. Implement a custom login module that retrieves the IP address of the standalone EJB client. > 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? > As soon as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12660) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12660?page=com.atlassian.jira.plugin... ] Farah Juma moved EAP7-1357 to WFLY-12660: ----------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-12660 (was: EAP7-1357) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Security (was: Security) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Product Docs (PD): (was: New) EAP PT Docs Analysis (DA): (was: TODO) Writer: (was: Tomas Radej) > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12660 > URL: https://issues.jboss.org/browse/WFLY-12660 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Minor > Labels: EAP-CD19, Previous_RFE, eap-7.2.0-deferred, eap-7.3.0-deferred > > UPDATE: > This requirement now applies to the new security implementation based on Elytron. > When a customer writes an authentication module using Elytron (similar to login module) where the custom code is involved in authenticating or authorizing , that user will be able to check the IP of the client that initiated the request so that they can auth decisions based on client IP. > ==================== > 2. Who is the customer behind the request? > Account: Alcatel - Canada (612917) > TAM customer: no > SRM customer: no > Strategic: no > 3. What is the nature and description of the request? > The customer wants to be able to get the IP address of the > EJB client in the login module when the security-realm is > configured to defer to jaas. > 4. Why does the customer need this? (List the business requirements here) > The customer needs the IP address of the client during the authentication process. > They use the IP address in their custom login module. > 5. How would the customer like to achieve this? (List the functional requirements here) > 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. > Configure the ApplicationRealm security-realm to defer to JAAS. Implement a custom login module that retrieves the IP address of the standalone EJB client. > 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? > As soon as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4707) OperationContext.getCapabilityServiceName(String, String...) generates wrong ServiceName if capability is not registered and dynamic part contains a DOT

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-4707: ------------------------------------ Summary: OperationContext.getCapabilityServiceName(String, String...) generates wrong ServiceName if capability is not registered and dynamic part contains a DOT Key: WFCORE-4707 URL: https://issues.jboss.org/browse/WFCORE-4707 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Jeff Mesnil Consider the call: {code:java} OperationContext.getCapabilityServiceName("test", "foo.bar"); {code} This method first resolves the qualified capability name as "test.foo.bar". If no capability is registered with that name, the service name is generated using: {code:java} ServiceNameFactory.parseServiceName("test.foo.bar"); {code} This generates a ServiceName with 3 elements. However, when this capability is actually created with name of "test" and dynamic part "foo.bar", its service name will contain 2 elements, not 3. i.e. {code:java} RuntimeCapability.Builder.of("test", true, ServiceType.class).fromBaseCapability("foo.bar").getCapabilityServiceName(); {code} Interestingly, the correspond method return by the OperationContext.getCapabilityServiceSupport() implementation does this correctly. i.e. {code:java} OperationContext.getCapabilityServiceSupport().getCapabilityServiceName("test", "foo.bar"); {code} returns the result of: {code:java} ServiceNameFactory.parseServiceName("test").append("foo.bar"); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-69) Upgrade WildFly Elytron 1.11.0.CR1

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-69?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-69: ----------------------------- Fix Version/s: 1.7.0.CR1 (was: 1.7.0.CR2) > Upgrade WildFly Elytron 1.11.0.CR1 > ---------------------------------- > > Key: ELYWEB-69 > URL: https://issues.jboss.org/browse/ELYWEB-69 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-69) Upgrade WildFly Elytron 1.11.0.CR1

by Farah Juma (Jira)

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

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-69) Upgrade WildFly Elytron 1.11.0.CR1

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-69?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-69: ----------------------------- Fix Version/s: 1.7.0.CR2 (was: 1.7.0.CR1) > Upgrade WildFly Elytron 1.11.0.CR1 > ---------------------------------- > > Key: ELYWEB-69 > URL: https://issues.jboss.org/browse/ELYWEB-69 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019