February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (ELY-1744) Remove use of java.security.acl APIs

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1744?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1744: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Remove use of java.security.acl APIs > ------------------------------------ > > Key: ELY-1744 > URL: https://issues.redhat.com/browse/ELY-1744 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.15.0.CR2 > > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within WildFly Elytron we only seem to use it in the JAAS security realm which I don't believe is used although likely is public API. I believe the use was to mirror some PicketBox behaviour. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1765?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1765: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.redhat.com/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.15.0.CR2 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1778) Enhanced Audit Logging - Feature parity with legacy audit logging

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1778?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1778: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Enhanced Audit Logging - Feature parity with legacy audit logging > ----------------------------------------------------------------- > > Key: ELY-1778 > URL: https://issues.redhat.com/browse/ELY-1778 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Justin Cook > Priority: Major > Fix For: 1.15.0.CR2 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for feature parity with legacy audit logging via: > * Additional audit events > * An "Audit" annotation -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1749?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1749: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.redhat.com/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.15.0.CR2 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1809) Update JAPICMP on a module by module basis

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1809?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1809: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Update JAPICMP on a module by module basis > ------------------------------------------ > > Key: ELY-1809 > URL: https://issues.redhat.com/browse/ELY-1809 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.15.0.CR2 > > > Each module should test it's own compatibility - however the compatible version should likely be defined in the root pom. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1808) Undertake further review of all duplicate packages to ensure we can make unique

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1808?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1808: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Undertake further review of all duplicate packages to ensure we can make unique > ------------------------------------------------------------------------------- > > Key: ELY-1808 > URL: https://issues.redhat.com/browse/ELY-1808 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.15.0.CR2 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1994: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.15.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-2074) SSO from FORM authentication required a distributed session

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2074?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2074: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > SSO from FORM authentication required a distributed session > ----------------------------------------------------------- > > Key: ELY-2074 > URL: https://issues.redhat.com/browse/ELY-2074 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.14.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.15.0.CR2 > > > Presently SSO only works on failover if also have a distributed HTTP session. > The SSO support is supposed to be operating independently of the session otherwise we should have just used the session to replicate the identity. I suspect that when we attempt to restore the identity we check if we have a session scope but as it does not exist we skip attempting the restoration, we should be open to restoration being possible without a session. > Overall however it feels like this approach will require some clean up which may be needed for ELY-1626 - instead of the current approach which intercepts session access and converts to SSO we may be better making SSO a real scope or something similar so mechanisms can interact directly with it. The approach today where we wrap the scope access and intercept the calls means mechanisms can easily make invalid assumptions about scope availability such as in this case. > The following TRACE logging shows a successful failover where a web application is marked as being distributed: > {code:java} > 2021-01-26 11:01:34,120 TRACE [org.wildfly.security.http.servlet] (default task-1) Created ServletSecurityContextImpl enableJapi=true, integratedJaspi=true, applicationContext=default-host /simple-webapp > 2021-01-26 11:01:34,121 TRACE [org.wildfly.security.http.servlet] (default task-1) No AuthConfigProvider for layer=HttpServlet, appContext=default-host /simple-webapp > 2021-01-26 11:01:34,121 TRACE [org.wildfly.security.http.servlet] (default task-1) JASPIC Unavailable, using HTTP authentication. > 2021-01-26 11:01:34,158 TRACE [org.wildfly.security] (default task-1) No CachedIdentity to restore. > 2021-01-26 11:01:34,158 TRACE [org.wildfly.security] (default task-1) Created HttpServerAuthenticationMechanism [org.wildfly.security.auth.server.SecurityIdentityServerMechanismFactory$1@4b6842ff] for mechanism [FORM] > 2021-01-26 11:01:34,160 TRACE [org.wildfly.security] (default task-1) Handling SocketAddressCallback > 2021-01-26 11:01:34,160 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='FORM' host-name='localhost' protocol='http' > 2021-01-26 11:01:34,160 TRACE [org.wildfly.security.http.form] (default task-1) Trying to re-authenticate session 3t7EGcnmInMeUYH3-thjyQpTyOanRdoX3Dm-BcS6. Request URI: [http://localhost:8080/simple-webapp/secured], Context path: [/simple-webapp] > 2021-01-26 11:01:34,160 TRACE [org.wildfly.security] (default task-1) Principal assigning: [alice], pre-realm rewritten: [alice], realm name: [example-realm], post-realm rewritten: [alice], realm rewritten: [alice] > 2021-01-26 11:01:34,165 TRACE [org.wildfly.security] (default task-1) Role mapping: principal [alice] -> decoded roles [Users, user] -> domain decoded roles [] -> realm mapped roles [Users, user] -> domain mapped roles [Users, user] > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Authorizing principal alice. > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Authorizing against the following attributes: [groups] => [user, Users] > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Authorizing against the following runtime attributes: [Source-Address] => [127.0.0.1] > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Permission mapping: identity [alice] with roles [Users, user] implies ("org.wildfly.security.auth.permission.LoginPermission" "") = true > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Authorization succeed > 2021-01-26 11:01:34,166 TRACE [org.wildfly.security] (default task-1) Handling CachedIdentityAuthorizeCallback: principal = alice authorizedIdentity = SecurityIdentity{principal=alice, securityDomain=org.wildfly.security.auth.server.SecurityDomain@61f54c5f, authorizationIdentity=EMPTY, realmInfo=RealmInfo{name='example-realm', securityRealm=org.wildfly.security.auth.realm.FileSystemSecurityRealm@78079856}, creationTime=2021-01-26T11:01:34.165503Z} > 2021-01-26 11:01:34,167 TRACE [org.wildfly.security] (default task-1) Handling AuthenticationCompleteCallback: succeed > 2021-01-26 11:01:34,167 TRACE [org.wildfly.security] (default task-1) Handling SecurityIdentityCallback: identity = SecurityIdentity{principal=alice, securityDomain=org.wildfly.security.auth.server.SecurityDomain@61f54c5f, authorizationIdentity=EMPTY, realmInfo=RealmInfo{name='example-realm', securityRealm=org.wildfly.security.auth.realm.FileSystemSecurityRealm@78079856}, creationTime=2021-01-26T11:01:34.165503Z} > 2021-01-26 11:01:34,168 TRACE [org.wildfly.security] (default task-1) Role mapping: principal [alice] -> decoded roles [Users, user] -> domain decoded roles [] -> realm mapped roles [Users, user] -> domain mapped roles [Users, user] {code} > > Where the web application is not distributed the following is logged instead: > {code:java} > 2021-01-26 11:26:14,189 INFO [org.infinispan.CLUSTER] (thread-10,ejb,nodea) ISPN100001: Node nodeb left the cluster > 2021-01-26 11:26:59,400 TRACE [org.wildfly.security.http.servlet] (default task-1) Created ServletSecurityContextImpl enableJapi=true, integratedJaspi=true, applicationContext=default-host /simple-webapp > 2021-01-26 11:26:59,400 TRACE [org.wildfly.security.http.servlet] (default task-1) No AuthConfigProvider for layer=HttpServlet, appContext=default-host /simple-webapp > 2021-01-26 11:26:59,400 TRACE [org.wildfly.security.http.servlet] (default task-1) JASPIC Unavailable, using HTTP authentication. > 2021-01-26 11:26:59,402 TRACE [org.wildfly.security] (default task-1) No CachedIdentity to restore. > 2021-01-26 11:26:59,402 TRACE [org.wildfly.security] (default task-1) Created HttpServerAuthenticationMechanism [org.wildfly.security.auth.server.SecurityIdentityServerMechanismFactory$1@71dc2149] for mechanism [FORM] > 2021-01-26 11:26:59,404 TRACE [org.wildfly.security] (default task-1) Handling SocketAddressCallback > 2021-01-26 11:26:59,404 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='FORM' host-name='localhost' protocol='http' > 2021-01-26 11:26:59,404 TRACE [org.wildfly.security.http.form] (default task-1) Trying to re-authenticate. There is no session attached to the following request. Request URI: [http://localhost:8080/simple-webapp/secured], Context path: [/simple-webapp] > 2021-01-26 11:26:59,404 TRACE [org.wildfly.security] (default task-1) Handling CachedIdentityAuthorizeCallback: principal = null authorizedIdentity = null {code} > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-2088) Revert Temporary Commit 68c2e952db67da0eebdde9ffcbec513a2af3f682

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2088?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2088: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Revert Temporary Commit 68c2e952db67da0eebdde9ffcbec513a2af3f682 > ---------------------------------------------------------------- > > Key: ELY-2088 > URL: https://issues.redhat.com/browse/ELY-2088 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.15.0.CR2 > > > Once WildFly has been updated for the changes related to ELY-1626 the following commit can be reverted: > > https://github.com/wildfly-security/wildfly-elytron/pull/1483/commits/68c... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-2089) Release WildFly Elytron 1.15.0.CR1

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2089?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-2089. ----------------------------- Resolution: Done > Release WildFly Elytron 1.15.0.CR1 > ---------------------------------- > > Key: ELY-2089 > URL: https://issues.redhat.com/browse/ELY-2089 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.15.0.CR1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

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 February 2021