[JBoss JIRA] (ELY-1225) Elytron - Write SASL mechanism implementing class into trace log
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1225?page=com.atlassian.jira.plugin.s... ]
Jan Kalina reopened ELY-1225:
-----------------------------
> Elytron - Write SASL mechanism implementing class into trace log
> ----------------------------------------------------------------
>
> Key: ELY-1225
> URL: https://issues.jboss.org/browse/ELY-1225
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.1.0.Beta50
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 1.1.0.Beta51
>
>
> It's very hard to debug issues when a wrong SASL mechanism implementation is used (e.g. JDK provided one instead Elytron one). The class name implementing the mechanism should be logged by Elytron.
> One place to cover this could be {{org.wildfly.security.auth.client.AuthenticationConfiguration.createSaslClient()}} method, but there are probably more places to look into.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (DROOLS-1551) Implement FEEL/DMN value marshaller
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1551?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-1551:
---------------------------------------
Implemented 2 marshallers:
FEELStringMarshaller: https://github.com/kiegroup/drools/pull/1345/files#diff-1912b09200f1836e5...
FEELCodeMarshaller: https://github.com/kiegroup/drools/pull/1345/files#diff-9bcf716d408c6a61f...
The main difference between them is that the String marshaller simply normalizes values and present them in a human readable format, while the Code marshaller produces a FEEL expression that can be executed to reconstruct the value.
For instance, marshalling the duration value P5Y2M with the String marshaller will result in:
P5Y2M
While using the Code marshaller will result in
duration( "P5Y2M" )
Both marshallers will normalize duration objects and set the negative sign, when appropriate, at the start of the expression as per the requirement.
> Implement FEEL/DMN value marshaller
> -----------------------------------
>
> Key: DROOLS-1551
> URL: https://issues.jboss.org/browse/DROOLS-1551
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Affects Versions: 7.0.0.CR3
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Priority: Critical
>
> Some value types in FEEL/DMN require special formatting when marshalling/unmarshalling. For instance:
> {quote}
> So it seems that ISO 8601 does not define negative intervals. I.e., ISO 8601 only supports things like "PT1H". XPath extends that with a leading optional sign, like "+PT1H" and "-PT1H". Java extends that allowing the sign to be used in each of the units in the duration like, "PT+1H", "PT-1H", besides the leading sign "-PT1H".
> The FEEL spec on page 113 seems to follow the XPath lexical definition, so the leading sign "-PT1H" seems to be the correct format.
> {quote}
> Implement an object marshaller for DMN/FEEL that is capable of marshalling/unmarshalling objects. Most object types are straightforward, but a few of them (like durations) need special handling. In particular:
> * negative duration should use a leading - sign instead of having the sign in the unit numbers
> * durations need to be normalized before marshalled:
> {quote}
> A days and time duration in the semantic domain is a sequence of numbers for the days, hours, minutes, and seconds of duration, normalized such that the sum of these numbers is minimized.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-261:
---------------------------------
Fix Version/s: 1.1.0.CR3
(was: 1.1.0.CR2)
> Rework (and move) UsernamePasswordHashUtil
> ------------------------------------------
>
> Key: ELY-261
> URL: https://issues.jboss.org/browse/ELY-261
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords
> Reporter: Darran Lofthouse
> Fix For: 1.1.0.CR3
>
>
> Firstly this class is not really SASL specific so should be in a general util package.
> Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (ELY-1272) Missing null checks in auth client lead to NPEs later on
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1272?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1272:
----------------------------------
Fix Version/s: 1.1.0.CR3
(was: 1.1.0.CR2)
> Missing null checks in auth client lead to NPEs later on
> --------------------------------------------------------
>
> Key: ELY-1272
> URL: https://issues.jboss.org/browse/ELY-1272
> Project: WildFly Elytron
> Issue Type: Bug
> Components: API / SPI, Authentication Client
> Reporter: David Lloyd
> Assignee: Stuart Douglas
> Fix For: 1.1.0.CR3
>
>
> There are missing null checks in at least the following places:
> * The constructor of org.wildfly.security.auth.principal.NamePrincipal which should require "name" to be non-null
> * The name argument to org.wildfly.security.auth.client.AuthenticationConfiguration#useName
> In addition, the following places handle null wrongly:
> * org.wildfly.security.auth.client.AuthenticationConfiguration#useAuthorizationName should check name for null, and if it is null, pass null in to useAuthorizationPrincipal
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months