[JBoss JIRA] (ELY-78) Move all classes to org.wildfly.sasl package
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-78?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-62 to ELY-78:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-78 (was: SASL-62)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: Build
(was: Build)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> Move all classes to org.wildfly.sasl package
> --------------------------------------------
>
> Key: ELY-78
> URL: https://issues.jboss.org/browse/ELY-78
> Project: WildFly Elytron
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> Will retain 'org.jboss.sasl.JBossSaslProvider' for backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-73) Make JBoss SASL an OSGi bundle
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-73?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-41 to ELY-73:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-73 (was: SASL-41)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: (was: 1.0.3.Final)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> Make JBoss SASL an OSGi bundle
> ------------------------------
>
> Key: ELY-73
> URL: https://issues.jboss.org/browse/ELY-73
> Project: WildFly Elytron
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Philippe Marschall
> Assignee: Darran Lofthouse
> Labels: osgi
> Fix For: 1.0.0.Beta1
>
>
> We'd like to deploy JBoss SASL in an OSGi environment (Equinox). For this is would be convenient for us if JBoss SASL was already an OSGi bundle and we don't have to wrap it.
> Pull request will follow shortly
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-70) AbstractSaslParticipant::evaluateMessage is not handling FAILED state correctly
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-70?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-69 to ELY-70:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-70 (was: SASL-69)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: (was: 2.0.0.Alpha1)
Component/s: SASL
(was: Util)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> AbstractSaslParticipant::evaluateMessage is not handling FAILED state correctly
> -------------------------------------------------------------------------------
>
> Key: ELY-70
> URL: https://issues.jboss.org/browse/ELY-70
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SASL
> Reporter: Peter Skopek
> Assignee: Peter Skopek
> Fix For: 1.0.0.Beta1
>
>
> When exception occurs down in state's evaluateMessage it always end up in the same state instead of FAILED state.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-72) Custom Property to Prefer JDK Mechanisms
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-72?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-49 to ELY-72:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-72 (was: SASL-49)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> Custom Property to Prefer JDK Mechanisms
> ----------------------------------------
>
> Key: ELY-72
> URL: https://issues.jboss.org/browse/ELY-72
> Project: WildFly Elytron
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> This is primarily for testing although it could be used for other purposes, a new custom property should be added to JBoss SASL which will cause mechanisms that duplicate JDK supplied mechanisms to avoid being used themselves.
> i.e. Even though JBoss SASL could supply an implementation for that mechanisms it will let the JDK supplied version win through.
> For testing this will enable interoperability testing between our mechanisms and the JDK mechanisms, for end users they could use JBoss SASL for the new mechanisms we supply whilst still using the JDK for the mechanisms it supplied.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-69) ByteStringBuilder constructor with initial byte array ignore this initial bytes
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-69?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-70 to ELY-69:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-69 (was: SASL-70)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: (was: 2.0.0.Alpha1)
Component/s: SASL
(was: Util)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> ByteStringBuilder constructor with initial byte array ignore this initial bytes
> -------------------------------------------------------------------------------
>
> Key: ELY-69
> URL: https://issues.jboss.org/browse/ELY-69
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SASL
> Reporter: Peter Skopek
> Assignee: Peter Skopek
> Fix For: 1.0.0.Beta1
>
>
> When one uses "new ByteStringBuilder(myByteArray)" the myByteArray is not included in the content of this ByteStringBuilder due to lenght field not set to initial length.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months