January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-931) PicketBoxMessages.authorizationFailedMessage misspelled Acces => Access

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-931?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-931: -------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1387278|https://bugzilla.redhat.com/show_bug.cgi?id=1387278] from VERIFIED to CLOSED > PicketBoxMessages.authorizationFailedMessage misspelled Acces => Access > ----------------------------------------------------------------------- > > Key: SECURITY-931 > URL: https://issues.jboss.org/browse/SECURITY-931 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Minor > > Acces should be Access in : > security-spi/common/src/main/java/org/jboss/security/PicketBoxMessages.java: @Message(id = 17, value = "Acces denied: authorization failed") -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1337) Support Elytron in security spi

by Flavia Rainone (JIRA)

Flavia Rainone created JBJCA-1337: ------------------------------------- Summary: Support Elytron in security spi Key: JBJCA-1337 URL: https://issues.jboss.org/browse/JBJCA-1337 Project: IronJacamar Issue Type: Feature Request Components: Core Environment: Make all adaptations necessary in IronJacamar to support JCA Elytron integration in Wildfly. Reporter: Flavia Rainone Assignee: Flavia Rainone -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7909) Bulk upgrade components

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7909: --------------------------------- Summary: Bulk upgrade components Key: WFLY-7909 URL: https://issues.jboss.org/browse/WFLY-7909 Project: WildFly Issue Type: Component Upgrade Components: Build System Affects Versions: 11.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Upgrade dependencies to use mostly latest versions where it is applicable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-835 at 1/18/17 8:59 AM: --------------------------------------------------------- [~dlofthouse] Do I understand correctly, this is what is supposed to work? {code:java} SecurityIdentity identity = trustingDomain.getAnonymousSecurityIdentity().createRunAsIdentity("joe", false); {code} (User "joe" exists in domain, which is in trusted-domains of trustingDomain.) Especialy this should give the same identity and roles as it would be called under the domain, where is "joe" present? was (Author: honza889): [~dlofthouse] Do I understand correctly, this is what is supposed to work? {code:java} SecurityIdentity inflowedIdentity = trustingDomain.getAnonymousSecurityIdentity().createRunAsIdentity("joe", false); {code} (User "joe" exists in domain, which is in trusted-domains of trustingDomain.) Especialy this should give the same identity and roles as it would be called under the domain, where is "joe" present? > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.1.0.Beta20 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-835: -------------------------------- [~dlofthouse] Do I understand correctly, this is what is supposed to work? {code:java} SecurityIdentity inflowedIdentity = trustingDomain.getAnonymousSecurityIdentity().createRunAsIdentity("joe", false); {code} (User "joe" exists in domain, which is in trusted-domains of trustingDomain.) Especialy this should give the same identity and roles as it would be called under the domain, where is "joe" present? > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.1.0.Beta20 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7908) Bulk upgrade components in WildFly

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7908: --------------------------------- Summary: Bulk upgrade components in WildFly Key: WFLY-7908 URL: https://issues.jboss.org/browse/WFLY-7908 Project: WildFly Issue Type: Component Upgrade Components: Build System Affects Versions: 11.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Upgrade dependencies to use mostly latest versions where it is applicable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7907) CLI command for update CredentialReference should fail rather then pass.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7907?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-7907: ---------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > CLI command for update CredentialReference should fail rather then pass. > ------------------------------------------------------------------------ > > Key: WFLY-7907 > URL: https://issues.jboss.org/browse/WFLY-7907 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > CLI command for update CredentialReference should fail rather then pass. > Because CLI command doesn't persist any data to configuration file but pass. > I expect that command would fail and shows some error message. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=credS004:add(uri="cr-store://test/credS004.jceks?create.storage=true", credential-reference={clear-text=pass987}, relative-to=jboss.server.data.dir) > {code} > {code} > /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference.store, value=credS002) > {code} > *AND* > {code} > /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference.alias, value=credS002) > {code} > *Ends with success, but it has to be a failure* > These commands could lead to inconsistency. > Because there is valid state to have > credential-reference={clear-text=pass987} > and credential-reference={store=cs, alias=alias} > but not their combination. > *I can use this right form of command* > {code} > /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference, value={store=credS002, alias=jimmy}) > {code} > Now is everything OK. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7907) CLI command for update CredentialReference should fail rather then pass.

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-7907: ---------------------------------- Summary: CLI command for update CredentialReference should fail rather then pass. Key: WFLY-7907 URL: https://issues.jboss.org/browse/WFLY-7907 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse CLI command for update CredentialReference should fail rather then pass. Because CLI command doesn't persist any data to configuration file but pass. I expect that command would fail and shows some error message. *How to reproduce* {code} /subsystem=elytron/credential-store=credS004:add(uri="cr-store://test/credS004.jceks?create.storage=true", credential-reference={clear-text=pass987}, relative-to=jboss.server.data.dir) {code} {code} /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference.store, value=credS002) {code} *AND* {code} /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference.alias, value=credS002) {code} *Ends with success, but it has to be a failure* These commands could lead to inconsistency. Because there is valid state to have credential-reference={clear-text=pass987} and credential-reference={store=cs, alias=alias} but not their combination. *I can use this right form of command* {code} /subsystem=elytron/credential-store=credS004:write-attribute(name=credential-reference, value={store=credS002, alias=jimmy}) {code} Now is everything OK. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7906) [GSS](7.0.x) Persistent calendar timer force logging for each invocation if the deployed-class has changed

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-7906: -------------------------------------- Summary: [GSS](7.0.x) Persistent calendar timer force logging for each invocation if the deployed-class has changed Key: WFLY-7906 URL: https://issues.jboss.org/browse/WFLY-7906 Project: WildFly Issue Type: Enhancement Components: EJB Reporter: Wolf-Dieter Fink Priority: Minor It will be common to change classes which contains @Schedule timer methods. In case such methods are removed or renamed (for persistent calendar timers) the server will log the following warning forever for each invocation. WARN [org.jboss.as.ejb3.timer] (EJB default - 1) WFLYEJB0161: Failed to reinstate timer 'ejb31-timer.ejb31-timer.SimpleScheduleSingletonTimerBean' (id=1a419372-d807-43d8-ac77-5be6696b022d) from its persistent state As this is intentional there should be a WARN message at (first) deployment time and the timer should be removed from the persistence. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4316) InvalidBytecodeException when an EJB local interface declares static method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4316?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4316: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1346242|https://bugzilla.redhat.com/show_bug.cgi?id=1346242] from VERIFIED to CLOSED > InvalidBytecodeException when an EJB local interface declares static method > --------------------------------------------------------------------------- > > Key: WFLY-4316 > URL: https://issues.jboss.org/browse/WFLY-4316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 9.0.0.Beta1 > > > {noformat} > Caused by: org.jboss.classfilewriter.InvalidBytecodeException: Cannot load variable at 1. Local Variables: Local Variables: [StackEntry [descriptor=Ljava/lang/String;, type=OBJECT]] > at org.jboss.classfilewriter.code.CodeAttribute.aload(CodeAttribute.java:185) > at org.jboss.invocation.proxy.ProxyFactory$ProxyMethodBodyCreator.overrideMethod(ProxyFactory.java:150) > at org.jboss.invocation.proxy.AbstractSubclassFactory.overrideMethod(AbstractSubclassFactory.java:106) > at org.jboss.invocation.proxy.AbstractSubclassFactory.addInterface(AbstractSubclassFactory.java:363) > at org.jboss.invocation.proxy.ProxyFactory.generateClass(ProxyFactory.java:286) > at org.jboss.invocation.proxy.AbstractClassFactory.buildClassDefinition(AbstractClassFactory.java:207) > at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:160) > at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:150) > at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:150) > at org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:68) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) > ... 6 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 January 2017