[jboss-jira] [JBoss JIRA] (ELY-159) Discovery of available algorithms for credential types

Darran Lofthouse (JIRA) issues at jboss.org
Wed Feb 25 07:17:49 EST 2015


    [ https://issues.jboss.org/browse/ELY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043529#comment-13043529 ] 

Darran Lofthouse commented on ELY-159:
--------------------------------------

Along similar lines as the original description here the realm needs to have access to some form of transformation utility for handling the transformation from one credential type + algorithm to another - i.e. the realm implementations should be able to be implemented with the bare minimum number of credential types supported - generally realms should only need to know about the types they use for storage.

As an example if a realm supports ClearPassword storage and retrieval the realm implementation should not now have the overhead of being able to convert to all credential types and it should also not have the overhead of having to be able to understand what can be translated to what.  At the same time where we can a mechanism implementation should just be using it's most specific password type implementation  and all this translation then happens at one central place.

> Discovery of available algorithms for credential types
> ------------------------------------------------------
>
>                 Key: ELY-159
>                 URL: https://issues.jboss.org/browse/ELY-159
>             Project: WildFly Elytron
>          Issue Type: Sub-task
>          Components: API / SPI
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 1.0.0.Alpha1
>
>
> The overall purpose of the getCredentialSupport calls is so that we can discover information about the supported credentials as authentication mechanisms are offered - the algorithm for the digest is just as important as knowing the general type.
> May just be a part of ELY-151 or may be something in addition.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list