[jboss-jira] [JBoss JIRA] (ELY-1261) Revisit credentials key-store-reference and certificate from Elytron client configuration file

[Farah Juma (JIRA)]

     [ https://issues.jboss.org/browse/ELY-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Farah Juma resolved ELY-1261.
-----------------------------
    Resolution: Rejected


Resolving this one since the corresponding JBEAP issue was rejected (it was decided that key-store-reference and certificate didn't need to be removed).

> Revisit credentials key-store-reference and certificate from Elytron client configuration file
> ----------------------------------------------------------------------------------------------
>
>                 Key: ELY-1261
>                 URL: https://issues.jboss.org/browse/ELY-1261
>             Project: WildFly Elytron
>          Issue Type: Bug
>    Affects Versions: 1.1.0.Beta52
>            Reporter: Ondrej Lukas
>            Priority: Critical
>
> It seems that only supported SASL mechanism in Elytron which is able to work with key/certificate is {{EXTERNAL}} mechanism. However this mechanism takes this information from SSL connection which means that credentials defined in {{configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference}} or {{configuration.authentication-client.authentication-configurations.configuration.credentials.certificate}} from Elytron client configuration file are not used in this case.
> Is there any Elytron supported SASL mechanism which is currently able to work with these credentials? In this case please provide configuration and SASL mechanism which is able to work with {{key-store-reference}} and {{certificate}} credentials.
> Otherwise these {{key-store-reference}} and {{certificate}} should be removed from Elytron client configuration because they currently cannot be used by users (or tested by QA). They can be added to configuration again once Elytron will support mechanism which is able to work with key/certificate as credentials. This is basically the similar issue as ELY-1257.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)