Re: Certificate Expiry (summary)

On 1/27/12 6:51 PM, Jürgen Jakobitsch wrote:
> hi kingsley,
>
> i think i'm gonna do something similar along the lines
> below. i just cannot do it with url-params since i have
> to stick to realm-api's methods.
>
> i notice that one stays logged on your verifier now,
> so two subsequent checks are not possible without
> clearing cache and cookies manually. if i remember
> it right that was previously not the case.

Hmmm.

I need to double check if something has changed in this new cut.

Kingsley
>
> wkr j
>
> ----- Original Message -----
> From: "Kingsley Idehen"<kidehen@openlinksw.com>
> To: public-webid@w3.org
> Sent: Saturday, January 28, 2012 12:18:48 AM
> Subject: Re: Certificate Expiry (summary)
>
> On 1/27/12 7:47 AM, Jürgen Jakobitsch wrote:
>> hi,
>>
>> is there a final conclusion on this issue yet,
>> which an implementor can rely on?
>>
>> i think it would be a good idea to write a couple
>> of lines into spec about this. from only reading
>> the spec now, i have no clue what to do with the dates
>> in a certificate.
>>
>> at current the best solution for WebIDRealm seems
>> to simply have some boolean flags that get read on startup.
>>
>> mindCertificateNotYetValid (=true|false)
>> mindCertificateExpired (=true|false)
>>
>> wkr j
> See: http://id.myopenlink.net/ods/webid_demo.html .
>
> For now we've made the expiration check optional.
>


-- 

Regards,

Kingsley Idehen 
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen