[jboss-jira] [JBoss JIRA] (ELY-1748) Add support for a BiFunction<T, U, V> to TokenSecurityRealm.Builder for the principalClaimName

[Farah Juma (Jira)]

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

Farah Juma updated ELY-1748:
----------------------------
    Fix Version/s: 2.0.0.Alpha1
                   1.9.0.CR1


> Add support for a BiFunction<T,U,V> to TokenSecurityRealm.Builder for the principalClaimName
> --------------------------------------------------------------------------------------------
>
>                 Key: ELY-1748
>                 URL: https://issues.jboss.org/browse/ELY-1748
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: Realms
>    Affects Versions: 1.7.0.Final
>            Reporter: Scott Stark
>            Assignee: Scott Stark
>            Priority: Major
>             Fix For: 2.0.0.Alpha1, 1.9.0.CR1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> I'm looking at using ELY to replace some of the custom auth code we have for the MP-JWT implementation in thorntail and elsewhere. While looking at using the org.wildfly.security.auth.realm.token.TokenSecurityRealm, I see that the claim used to extract the principal name from the token is a fixed claim name. In the MP-JWT spec we allow for a series of claims to be checked in a given order to attempt to obtain the principal name. What is needed is a BiFunction<BearerTokenEvidence,Attributes,String> or perhaps just a Funtion<Attributes,String> principalClaimNameFunction() method on the Builder to externalize the claim to principal name mapping.
> I'll look at creating a pull request for this.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)