On 26.5.2014 18:23, Nathaniel McCallum wrote:
On Mon, 2014-05-26 at 09:56 +0200, Jan Cholasta wrote:
On 23.5.2014 23:19, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
Occasionally OTP tokens get out of sync with the server. When this
happens, the user o
On Mon, 2014-05-26 at 09:56 +0200, Jan Cholasta wrote:
> On 23.5.2014 23:19, Nathaniel McCallum wrote:
> > On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
> >> Occasionally OTP tokens get out of sync with the server. When this
> >> happens, the user or an admin need to synchronize the
On 26.5.2014 09:41, Martin Kosek wrote:
On 05/23/2014 11:19 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
Occasionally OTP tokens get out of sync with the server. When this
happens, the user or an admin need to synchronize the token. To this
end, we
On 23.5.2014 23:19, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
Occasionally OTP tokens get out of sync with the server. When this
happens, the user or an admin need to synchronize the token. To this
end, we landed server-side synchronization support, w
On 05/23/2014 11:19 PM, Nathaniel McCallum wrote:
> On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
>> Occasionally OTP tokens get out of sync with the server. When this
>> happens, the user or an admin need to synchronize the token. To this
>> end, we landed server-side synchronizatio
On Wed, 2014-05-14 at 14:08 -0400, Nathaniel McCallum wrote:
> Occasionally OTP tokens get out of sync with the server. When this
> happens, the user or an admin need to synchronize the token. To this
> end, we landed server-side synchronization support, which is a simple
> bind with a custom contr
On Wed, May 14, 2014 at 05:23:34PM -0400, Nathaniel McCallum wrote:
> > IMO SSSD should probably have a way to sync the token.
> > From usability point of view it should be a part of the standard stock
> > client software, not a part of the IPA client or ipa tools.
> > It should probably have a go
On 15.5.2014 00:23, Dmitri Pal wrote:
On 05/14/2014 05:49 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 17:35 -0400, Dmitri Pal wrote:
On 05/14/2014 05:23 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 16:34 -0400, Dmitri Pal wrote:
On 05/14/2014 02:08 PM, Nathaniel McCallum wrote:
On 15.5.2014 09:52, Simo Sorce wrote:
- Original Message -
Occasionally OTP tokens get out of sync with the server. When this
happens, the user or an admin need to synchronize the token. To this
end, we landed server-side synchronization support, which is a simple
bind with a custom co
- Original Message -
> Occasionally OTP tokens get out of sync with the server. When this
> happens, the user or an admin need to synchronize the token. To this
> end, we landed server-side synchronization support, which is a simple
> bind with a custom control. This all works with my sam
On 05/14/2014 05:49 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 17:35 -0400, Dmitri Pal wrote:
On 05/14/2014 05:23 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 16:34 -0400, Dmitri Pal wrote:
On 05/14/2014 02:08 PM, Nathaniel McCallum wrote:
Occasionally OTP tokens get out of sy
On Wed, 2014-05-14 at 17:35 -0400, Dmitri Pal wrote:
> On 05/14/2014 05:23 PM, Nathaniel McCallum wrote:
> > On Wed, 2014-05-14 at 16:34 -0400, Dmitri Pal wrote:
> >> On 05/14/2014 02:08 PM, Nathaniel McCallum wrote:
> >>> Occasionally OTP tokens get out of sync with the server. When this
> >>> hap
On 05/14/2014 05:23 PM, Nathaniel McCallum wrote:
On Wed, 2014-05-14 at 16:34 -0400, Dmitri Pal wrote:
On 05/14/2014 02:08 PM, Nathaniel McCallum wrote:
Occasionally OTP tokens get out of sync with the server. When this
happens, the user or an admin need to synchronize the token. To this
end, w
On Wed, 2014-05-14 at 16:34 -0400, Dmitri Pal wrote:
> On 05/14/2014 02:08 PM, Nathaniel McCallum wrote:
> > Occasionally OTP tokens get out of sync with the server. When this
> > happens, the user or an admin need to synchronize the token. To this
> > end, we landed server-side synchronization sup
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
> In attempting to write an OTP synchronization client, I've noticed it
> doesn't fit into the framework very well. The job of the client is to
> perform the synchronization extended operation. The format of the
> request is this:
>
>
On 01/23/2014 09:41 AM, Nathaniel McCallum wrote:
> On Thu, 2014-01-23 at 10:28 +0100, Petr Vobornik wrote:
>> On 22.1.2014 22:07, Nathaniel McCallum wrote:
>>> On Wed, 2014-01-22 at 16:03 -0500, Rob Crittenden wrote:
Nathaniel McCallum wrote:
> In attempting to write an OTP synchronizatio
Nathaniel McCallum wrote:
On Thu, 2014-01-23 at 16:27 +0100, Jan Cholasta wrote:
Hi,
On 23.1.2014 16:19, Rob Crittenden wrote:
Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't
On 01/23/2014 07:33 PM, Nathaniel McCallum wrote:
On Thu, 2014-01-23 at 16:27 +0100, Jan Cholasta wrote:
Hi,
On 23.1.2014 16:19, Rob Crittenden wrote:
Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client,
On Thu, 2014-01-23 at 16:27 +0100, Jan Cholasta wrote:
> Hi,
>
> On 23.1.2014 16:19, Rob Crittenden wrote:
> > Nathaniel McCallum wrote:
> >> On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
> >>> In attempting to write an OTP synchronization client, I've noticed it
> >>> doesn't fit i
Hi,
On 23.1.2014 16:19, Rob Crittenden wrote:
Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't fit into the framework very well. The job of the client is to
perform the synchroni
Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't fit into the framework very well. The job of the client is to
perform the synchronization extended operation. The format of the
req
On Wed, 2014-01-22 at 15:59 -0500, Nathaniel McCallum wrote:
> In attempting to write an OTP synchronization client, I've noticed it
> doesn't fit into the framework very well. The job of the client is to
> perform the synchronization extended operation. The format of the
> request is this:
>
>
On Thu, 2014-01-23 at 10:28 +0100, Petr Vobornik wrote:
> On 22.1.2014 22:07, Nathaniel McCallum wrote:
> > On Wed, 2014-01-22 at 16:03 -0500, Rob Crittenden wrote:
> >> Nathaniel McCallum wrote:
> >>> In attempting to write an OTP synchronization client, I've noticed it
> >>> doesn't fit into the
On 22.1.2014 22:07, Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 16:03 -0500, Rob Crittenden wrote:
Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't fit into the framework very well. The job of the client is to
perform the synchronizatio
Nathaniel McCallum wrote:
On Wed, 2014-01-22 at 16:03 -0500, Rob Crittenden wrote:
Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't fit into the framework very well. The job of the client is to
perform the synchronization extended operation
On Wed, 2014-01-22 at 16:03 -0500, Rob Crittenden wrote:
> Nathaniel McCallum wrote:
> > In attempting to write an OTP synchronization client, I've noticed it
> > doesn't fit into the framework very well. The job of the client is to
> > perform the synchronization extended operation. The format of
Nathaniel McCallum wrote:
In attempting to write an OTP synchronization client, I've noticed it
doesn't fit into the framework very well. The job of the client is to
perform the synchronization extended operation. The format of the
request is this:
OTPSyncRequestValue ::= SEQUENCE {
27 matches
Mail list logo
