[JBoss JIRA] (ELY-613) Some nested classes should be considered to be static nested in Elytron
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-613?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-613:
------------------------------------
Assignee: (was: Darran Lofthouse)
> Some nested classes should be considered to be static nested in Elytron
> -----------------------------------------------------------------------
>
> Key: ELY-613
> URL: https://issues.jboss.org/browse/ELY-613
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta7
> Reporter: Ondrej Lukas
> Labels: static_analysis
> Fix For: 1.2.0.Beta1
>
>
> There are some inner classes in Elytron which should be considered to be static nested to avoid dependency on their outer class. Following nested classes should be considered:
> * LoadedIdentity and Identity from org.wildfly.security.auth.realm.FileSystemSecurityRealm
> * DecoderState from org.wildfly.security.asn1.DERDecoder
> * AccountEntry from org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm
> * JaasAuthorizationIdentity and DefaultCallbackHandler from org.wildfly.security.auth.realm.JaasSecurityRealm
> * LoadKey from org.wildfly.security.keystore.AtomicLoadKeyStore
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-376) Password policies
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-376?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-376:
------------------------------------
Assignee: (was: David Lloyd)
> Password policies
> -----------------
>
> Key: ELY-376
> URL: https://issues.jboss.org/browse/ELY-376
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords, Realms
> Reporter: Darran Lofthouse
> Fix For: 2.0.0.Alpha1
>
>
> Probably needs a design discussion first but we need to review where password policies fit in to the overall solution.
> We may say that policy handling is really the responsibility of the actual realm implementation, after all items such as history are going to be very realm specific.
> However there may also be a case in the generic sense that where a modifiable realm is in use a policy is desired to cover the complexity of any passwords set on that realm.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-483) GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-483?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-483:
------------------------------------
Assignee: (was: Darran Lofthouse)
> GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK
> ----------------------------------------------------------------------------------------------------
>
> Key: ELY-483
> URL: https://issues.jboss.org/browse/ELY-483
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta5
> Reporter: Ondrej Lukas
>
> Test cases initialization from GssapiTestSuite and Gs2Test fail with following exception for IBM JDK:
> {code}
> javax.security.auth.login.FailedLoginException:
> Login error: com.ibm.security.krb5.KrbException, status code: 9
> message: The client or server has a null key
> at com.ibm.security.jgss.i18n.I18NException.throwFailedLoginException(I18NException.java:15)
> at com.ibm.security.auth.module.Krb5LoginModule.j(Krb5LoginModule.java:727)
> at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:307)
> at com.ibm.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:59)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:788)
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:196)
> at javax.security.auth.login.LoginContext$5.run(LoginContext.java:721)
> at javax.security.auth.login.LoginContext$5.run(LoginContext.java:719)
> at java.security.AccessController.doPrivileged(AccessController.java:686)
> at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:719)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:593)
> at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71)
> at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53)
> at org.wildfly.security.sasl.gssapi.JdkClientJdkServer.initialise(JdkClientJdkServer.java:47)
> ...
> {code}
> It is test case issue but it can hide any another functional issue because affected tests are not running with IBM JDK.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-678) Credential-reference(alias=) should be resolved in time of request.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-678?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-678:
------------------------------------
Assignee: (was: Peter Skopek)
> Credential-reference(alias=) should be resolved in time of request.
> -------------------------------------------------------------------
>
> Key: ELY-678
> URL: https://issues.jboss.org/browse/ELY-678
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Affects Versions: 1.1.0.Beta10
> Reporter: Hynek Švábek
> Attachments: credentialstore.jceks, firefly.keystore
>
>
> Credential-reference should be resolved in time of request - in this case the alias which contains wrong password in CredentialStore (we can change it later to right password...).
> If I add credential reference with alias which contains wrong password then I get this error:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.fireflyWrong" => "org.jboss.msc.service.StartException in service org.wildfly.security.key-store.fireflyWrong: WFLYELY00004: Unable to start the service.
> Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
> Caused by: java.security.UnrecoverableKeyException: Password verification failed"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.key-store.fireflyWrong"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> *When I reload server then same command pass!*
> But I nowhere got information about reload-required
> {code}
> /subsystem=elytron/key-store=fireflyWrong:add(path=cs/firefly.keystore,relative-to=jboss.server.data.dir,type=JKS,credential-reference= {store=credStore2,alias=ffWithWrongPass})
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-97) Realm Readniess
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-97?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse reassigned ELY-97:
-----------------------------------
Assignee: (was: Darran Lofthouse)
> Realm Readniess
> ---------------
>
> Key: ELY-97
> URL: https://issues.jboss.org/browse/ELY-97
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI
> Reporter: Darran Lofthouse
> Fix For: 1.2.0.Beta1
>
>
> Needs some discussion first but this is along the lines of the following: -
> 1 - Within WildFly where we currently have realms we have an ability to query them to check they are ready to handle requests - this is mainly used for out of the box where we can display an error page describing to the user additional steps they need to perform.
> 2 - Realms are essentially the interface to back end stores of user information, most likely being remote with no guarantee that they are always available, from an Elytron perspective this adds an additional two options: -
> i. Alter offered realms also taking into account availability, information disclosure risk but worth considering.
> ii. Security status panels within admin console, view at a glance what is available and what is not allowing administrator to take action. We also have notification support - a candidate for a notification.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months