November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-335) Catching custom login module exceptions in remote client

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-335?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved WFLY-335. ----------------------------------- Fix Version/s: 11.0.0.Alpha1 Resolution: Out of Date Migrating to WildFly Elytron away from JAAS login modules. > Catching custom login module exceptions in remote client > -------------------------------------------------------- > > Key: WFLY-335 > URL: https://issues.jboss.org/browse/WFLY-335 > Project: WildFly > Issue Type: Feature Request > Components: Remoting, Security, Server > Environment: Win 7 64 Bit > 4 GB RAM > java 1.6 > Reporter: Serkan Yıldırım > Assignee: Darran Lofthouse > Labels: exception, login, login-module, remoting > Fix For: 11.0.0.Alpha1 > > > This feature request is related with the discussion: > https://community.jboss.org/message/732948#732948 > I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client. Darran said that it's not supported in this version. I think it is a necessary feature because a remote user could be informed why login is failed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-319) OpenSSL SSL certificate support for domain management security realms (http and native interface)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-319?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved WFLY-319. ----------------------------------- Resolution: Out of Date Management is migrated to use Elytron capabilities, OpenSSL support will be added through Wildfly Elytron. > OpenSSL SSL certificate support for domain management security realms (http and native interface) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-319 > URL: https://issues.jboss.org/browse/WFLY-319 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security, Server > Reporter: Franck LEDAY > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > related to https://community.jboss.org/message/728665#728665 : > Request the feature to use SSL certificate issued from OpenSSL directly from SSL attribute of management interface instead of available use of JKS . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-414) Add a non-caching authentication cache

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-414?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved WFLY-414. ----------------------------------- Fix Version/s: 11.0.0.Alpha1 Resolution: Out of Date The new security architecture is based on WildFly Elytron > Add a non-caching authentication cache > -------------------------------------- > > Key: WFLY-414 > URL: https://issues.jboss.org/browse/WFLY-414 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Add an option to either disable the authentication cache or a cache implementation that does not cache. > This is for incoming requests where we do not have a username and password available to use to retrieve an verify items from a cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1056) Certificate to principal mapping

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1056?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-1056. ------------------------------------ Fix Version/s: 11.0.0.Alpha1 Resolution: Out of Date Migration to Elytron will be providing much more advanced certificate based authentication and already includes certificate to identity mapping. > Certificate to principal mapping > -------------------------------- > > Key: WFLY-1056 > URL: https://issues.jboss.org/browse/WFLY-1056 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Yves Peter > Assignee: Anil Saldanha > Fix For: 11.0.0.Alpha1 > > > In JBoss 7 it is no longer possible to configure how a certificate is mapped to a principal using client-cert authentication. The dynamic code was removed in JBoss 7 in the JBossWebRealm and is now hard coded to use the SubjectDNMapping: > http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... > http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... > Also the JBossWebRealm does only consider role- but no principal-mapping modules. > We use this to authenticate users against an ldap server where the dn of the user doesn't match the dn in the ldap server. Also it's useful for display purpose in an application. > An example and some further information is in the linked user form thread. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1136) Common mechanism for all secure socket definitions

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1136?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-1136. ------------------------------------ Resolution: Done Resolving as the Elytron integration now provided capabilities for various SSL types - individual subsystems will continue to be migrated independently to use these. > Common mechanism for all secure socket definitions > -------------------------------------------------- > > Key: WFLY-1136 > URL: https://issues.jboss.org/browse/WFLY-1136 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: > >> The JAASSecurityDomain in my opinion should > >> handle all secure socket definitions. Mod-cluster currently does > >> not support JAASSecurityDomains. > I won't comment either way on whether JAASSecurityDomain is how we'll do this, but I definitely agree that a common mechanism should be used for all secure socket definitions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7552) Elytron mapped-regex-realm-mapper "pattern" and "name" attributs have wrong description.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7552?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved WFCORE-1925 to WFLY-7552: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-7552 (was: WFCORE-1925) Component/s: Security (was: Security) > Elytron mapped-regex-realm-mapper "pattern" and "name" attributs have wrong description. > ---------------------------------------------------------------------------------------- > > Key: WFLY-7552 > URL: https://issues.jboss.org/browse/WFLY-7552 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > Elytron mapped-regex-realm-mapper "pattern" and "name" attributes have wrong description [1]. > *Actual description* > {code} > The regular expression to use for this NameRewriter. > {code} > *Expected description* > Some like that (from DMR): > {code} > The regular expression which must contain at least one capture group to extract the realm from the name. > {code} > [1] https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7550) Manifest Validation Error

by Rohit Lakshykar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7550?page=com.atlassian.jira.plugin.... ] Rohit Lakshykar updated WFLY-7550: ---------------------------------- Security: (was: Red Hat Internal) > Manifest Validation Error > ------------------------- > > Key: WFLY-7550 > URL: https://issues.jboss.org/browse/WFLY-7550 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 10.1.0.Final > Reporter: Rohit Lakshykar > Assignee: David Lloyd > Priority: Blocker > > Facing issue while deploying application. > description available here > http://stackoverflow.com/questions/40507281/jboss-wildfly-java-io-ioexcep... > I have checked manifest file and working fine on other servers except wildfly > 17:24:51,665 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."axiswebservice.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."axiswebservice.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "axiswebservice.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0161: Failed to get manifest for deployment "/content/axiswebservice.war/WEB-INF/lib/AxisBankEncDemov1.0.jar" > at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:78) > at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:65) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: java.io.IOException: invalid manifest format > at java.util.jar.Manifest.read(Manifest.java:225) > at java.util.jar.Manifest.<init>(Manifest.java:69) > at org.jboss.vfs.VFSUtils.readManifest(VFSUtils.java:243) > at org.jboss.vfs.VFSUtils.getManifest(VFSUtils.java:227) > at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:76) > ... 7 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7551) Elytron simple-regex-realm-mapper "pattern" attribute has wrong description.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7551?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved WFCORE-1924 to WFLY-7551: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-7551 (was: WFCORE-1924) Component/s: Security (was: Security) > Elytron simple-regex-realm-mapper "pattern" attribute has wrong description. > ---------------------------------------------------------------------------- > > Key: WFLY-7551 > URL: https://issues.jboss.org/browse/WFLY-7551 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > Elytron simple-regex-realm-mapper "pattern" attribute has wrong description [1]. > *Actual description* > {code} > The regular expression to use for this NameRewriter. > {code} > *Expected description* > Some like that (from DMR): > {code} > The regular expression which must contain at least one capture group to extract the realm from the name. > {code} > [1] https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1731) Exception generated from command "connection-info" with embedded server

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1731?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1731: ------------------------------------------ Now that our pull request has been merged to Core it would be a good time to review this one again and see if the error is still present. > Exception generated from command "connection-info" with embedded server > ----------------------------------------------------------------------- > > Key: WFCORE-1731 > URL: https://issues.jboss.org/browse/WFCORE-1731 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management, Security > Affects Versions: 3.0.0.Alpha5 > Environment: JBoss Admin Command-line Interface > JBOSS_HOME: C:\dev\jboss-eap-7.0.1 > JBoss AS release: 2.1.6.Final-redhat-1 "Kenny" > JBoss AS product: JBoss EAP 7.0.1.GA > JAVA_HOME: c:\java\jdk1.8.0_45 > java.version: 1.8.0_45 > java.vm.vendor: Oracle Corporation > java.vm.version: 25.45-b02 > os.name: Windows 7 > os.version: 6.1 > Reporter: Petr Kremensky > Assignee: Ingo Weiss > Priority: Minor > > I started the embedded server and tried to obtain the connection information. An exception occurred: > {code} > [standalone@embedded /] connection-info > 13:14:59,095 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 32) WFLYCTL0013: Operation ("whoami") failed - address: ([]): java.lang.IllegalArgumentException: newValue is null > at org.jboss.dmr.ModelNode.set(ModelNode.java:499) > at org.jboss.as.domain.management.security.WhoAmIOperation.execute(WhoAmIOperation.java:95) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649) > at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63) > at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.java:59) > at org.jboss.as.cli.handlers.ConnectionInfoHandler.doHandle(ConnectionInfoHandler.java:74) > at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:88) > at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:776) > at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:799) > at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:412) > at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: newValue is null > Failed to handle 'connection-info': java.lang.NullPointerException > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1701) In-VM Identity Representation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1701?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-1701. -------------------------------------- Fix Version/s: 3.0.0.Alpha12 (was: 3.0.0.Alpha13) Resolution: Done Resolving as we have an initial implementation in 3.0.0.Alpha12 - an additional issue has been raised to follow up further. > In-VM Identity Representation > ----------------------------- > > Key: WFCORE-1701 > URL: https://issues.jboss.org/browse/WFCORE-1701 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha12 > > > If Elytron has no current SecurityIdentity then an anonymous identity is used. The issue however is that this anonymous identity could be because the current user does not have access to be inflowed to the SecurityDomain being used for management or it could be because it is an in-vm call and no identity is established. > We need a solution to safely represent an in-vm call and differentiate it from a user with no appropriate identity, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016