[JBoss JIRA] (ELY-535) Add the ability to handle password updates and resets for the OTP SASL mechanism
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-535?page=com.atlassian.jira.plugin.sy... ]
Farah Juma commented on ELY-535:
--------------------------------
As mentioned in [PR #441|https://github.com/wildfly-security/wildfly-elytron/pull/441], instead of using events, we can add a method to {{RealmIdentity}} to handle updating a credential.
> Add the ability to handle password updates and resets for the OTP SASL mechanism
> --------------------------------------------------------------------------------
>
> Key: ELY-535
> URL: https://issues.jboss.org/browse/ELY-535
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: SASL
> Reporter: Farah Juma
> Assignee: Farah Juma
>
> For the OTP SASL mechanism, the stored credential needs to be updated once a guess has been verified. In the standard case, this involves updating the stored hash based on the guess and decrementing the sequence number by 1. The OTP SASL mechanism also supports OTP sequence resets, where a user provides both a guess and a new OTP password with new parameters. If verification of the guess succeeds, then the stored credential is updated based on the new password and new parameters. However, if verification of the guess succeeds but the new password/parameters are invalid, then the stored hash is updated based on the guess and the sequence number is decremented by 1, as in the non-reset case (note that SASL auth fails in this case though).
> PR #277 [adds handling|https://github.com/kabir/wildfly-elytron/blob/otp-test/src/main/...] for a {{CredentialUpdateCallback}} in {{ServerAuthenticationContext}}. This is used to handle both the OTP sequence reset case as well as the non-reset case. Instead of manipulating the realm identity directly in the SAC callback handler, we should be able to make use of [realm events|https://github.com/wildfly-security/wildfly-elytron/pull/295] so that the realm itself can handle OTP updates and resets.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-535) Add the ability to handle password updates and resets for the OTP SASL mechanism
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-535?page=com.atlassian.jira.plugin.sy... ]
Farah Juma updated ELY-535:
---------------------------
Summary: Add the ability to handle password updates and resets for the OTP SASL mechanism (was: Make use of realm events to handle password updates and resets for the OTP SASL mechanism)
> Add the ability to handle password updates and resets for the OTP SASL mechanism
> --------------------------------------------------------------------------------
>
> Key: ELY-535
> URL: https://issues.jboss.org/browse/ELY-535
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: SASL
> Reporter: Farah Juma
> Assignee: Farah Juma
>
> For the OTP SASL mechanism, the stored credential needs to be updated once a guess has been verified. In the standard case, this involves updating the stored hash based on the guess and decrementing the sequence number by 1. The OTP SASL mechanism also supports OTP sequence resets, where a user provides both a guess and a new OTP password with new parameters. If verification of the guess succeeds, then the stored credential is updated based on the new password and new parameters. However, if verification of the guess succeeds but the new password/parameters are invalid, then the stored hash is updated based on the guess and the sequence number is decremented by 1, as in the non-reset case (note that SASL auth fails in this case though).
> PR #277 [adds handling|https://github.com/kabir/wildfly-elytron/blob/otp-test/src/main/...] for a {{CredentialUpdateCallback}} in {{ServerAuthenticationContext}}. This is used to handle both the OTP sequence reset case as well as the non-reset case. Instead of manipulating the realm identity directly in the SAC callback handler, we should be able to make use of [realm events|https://github.com/wildfly-security/wildfly-elytron/pull/295] so that the realm itself can handle OTP updates and resets.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-563) Clean up SSLExplorer
by David Lloyd (JIRA)
David Lloyd created ELY-563:
-------------------------------
Summary: Clean up SSLExplorer
Key: ELY-563
URL: https://issues.jboss.org/browse/ELY-563
Project: WildFly Elytron
Issue Type: Task
Components: SSL
Reporter: David Lloyd
Priority: Minor
The code in SSLExplorer works but it's pretty ugly and could be cleaned up to be marginally more efficient and neater.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-562) Add cipher suite information to SSLConnectionInformation
by David Lloyd (JIRA)
David Lloyd created ELY-562:
-------------------------------
Summary: Add cipher suite information to SSLConnectionInformation
Key: ELY-562
URL: https://issues.jboss.org/browse/ELY-562
Project: WildFly Elytron
Issue Type: Feature Request
Components: SSL
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.1.0.Beta6
Add cipher suites to the SSL context selection process. This may help with HTTP/2.0 in the future, among other things.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months