[JBoss JIRA] (WFCORE-2912) Changes to support Elytron API change
by David Lloyd (JIRA)
David Lloyd created WFCORE-2912:
-----------------------------------
Summary: Changes to support Elytron API change
Key: WFCORE-2912
URL: https://issues.jboss.org/browse/WFCORE-2912
Project: WildFly Core
Issue Type: Task
Reporter: David Lloyd
Assignee: David Lloyd
In Elytron 1.1.0.Beta50, a change in the {{SecurityRealm}} and {{RealmIdentity}} interfaces means that implementations will break if they do not add new method(s). This issue is to track this change.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-2913) Changes to support Elytron API change
by David Lloyd (JIRA)
David Lloyd created WFCORE-2913:
-----------------------------------
Summary: Changes to support Elytron API change
Key: WFCORE-2913
URL: https://issues.jboss.org/browse/WFCORE-2913
Project: WildFly Core
Issue Type: Task
Reporter: David Lloyd
Assignee: David Lloyd
In Elytron 1.1.0.Beta50, a change in the {{SecurityRealm}} and {{RealmIdentity}} interfaces means that implementations will break if they do not add new method(s). This issue is to track this change.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1207) Incorrectly named attribute match-user in authentication-context in Elytron subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1207?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1207:
----------------------------------
Fix Version/s: 1.1.0.Beta49
(was: 1.1.0.Beta48)
> Incorrectly named attribute match-user in authentication-context in Elytron subsystem
> -------------------------------------------------------------------------------------
>
> Key: ELY-1207
> URL: https://issues.jboss.org/browse/ELY-1207
> Project: WildFly Elytron
> Issue Type: Bug
> Components: XML
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Critical
> Labels: user_experience
> Fix For: 1.1.0.Beta49
>
>
> Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching.
> Also description in CLI is not correct, it says: _The user to match against._
> It means one of following should be changed:
> * name of {{match-user}}
> * functionality of {{MatchUserRule}}
> Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1199) Credential store, during creation of CS backed keystore is not created on filesystem.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1199?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1199:
----------------------------------
Fix Version/s: 1.1.0.Beta49
> Credential store, during creation of CS backed keystore is not created on filesystem.
> -------------------------------------------------------------------------------------
>
> Key: ELY-1199
> URL: https://issues.jboss.org/browse/ELY-1199
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta46
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Labels: credential-store
> Fix For: 1.1.0.Beta49
>
>
> Keystore is created after writing secret key into it. So instead of "write alias" operation it is more "write alias and create backed keystore if not exists yet" operation.
> How to reproduce:
> - create credential store from scratch
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/credential-store=myCredStore:add(uri="cr-store://test/myCredStore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to=jboss.server.config.dir)
> {"outcome" => "success"}
> {code}
> - myCredStore.jceks does not exists on FS (I would expect it will be created)
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/credential-store=myCredStore/alias=myAlias:add(secret-value=secret)
> {"outcome" => "success"}
> {code}
> - myCredStore.jceks exists on FS
> Setting high priority as lack of this behaviour can lead to more complex problems in multiprocess scenarios (e.g domain mode)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months