Re: [scim] User extension for not valid before / after ?

Radovan Semancik <radovan.semancik@evolveum.com> Thu, 08 September 2022 06:10 UTC

Return-Path: <radovan.semancik@evolveum.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47D46C14F746 for <scim@ietfa.amsl.com>; Wed, 7 Sep 2022 23:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=evolveum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNp_y-K2yYC5 for <scim@ietfa.amsl.com>; Wed, 7 Sep 2022 23:10:51 -0700 (PDT)
Received: from zimbra.evolveum.com (zimbra.evolveum.com [185.50.215.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E891CC14F72B for <scim@ietf.org>; Wed, 7 Sep 2022 23:10:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zimbra.evolveum.com (Postfix) with ESMTP id 6381C5365E9 for <scim@ietf.org>; Thu, 8 Sep 2022 08:10:46 +0200 (CEST)
Received: from zimbra.evolveum.com ([127.0.0.1]) by localhost (zimbra.evolveum.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3tjhni5iHyyg for <scim@ietf.org>; Thu, 8 Sep 2022 08:10:46 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.evolveum.com (Postfix) with ESMTP id 2ED0F5365BE for <scim@ietf.org>; Thu, 8 Sep 2022 08:10:46 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbra.evolveum.com 2ED0F5365BE
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evolveum.com; s=993730DA-531D-11E9-B3C4-8B623A39D637; t=1662617446; bh=yh8MuTYOjC8Ve3Hy0RsWVMyhzzXswkd8rYH9IPfeT9c=; h=Message-ID:Date:MIME-Version:To:From; b=X/27HIq6McnETUxEWQYEGEq7VEIRMKTv9KQAwe+rHx+BoF1vXO2z9qtElJBpAElGI MHITu6iDYKJX/CiH6HRi5mt/b48hpAvNaJJlT4JJGM4epLuDknGyE8ldxpRMaLNbwP BpoZA16h6H+UwE3P5L+SeEzeRc0uyZmDDyBuuDh+29TkeVQOUsuJBBQZFjc3AS1UFP VGjT8wqXgx9PbtzcSb9Nmcd0glSjWc7A3bi1bjR6W+a6XnC5mqNMBOvsPotYqPPxMT 2CtKnTYzGkb5RxgU2MphkYq3RA7n88Wmo3PSerrSFO8S2fXRRPZC0qFmnD8+kiYGu4 BNM3umit6iAKA==
X-Virus-Scanned: amavisd-new at zimbra.evolveum.com
Received: from zimbra.evolveum.com ([127.0.0.1]) by localhost (zimbra.evolveum.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rz56eFRFt3Mm for <scim@ietf.org>; Thu, 8 Sep 2022 08:10:46 +0200 (CEST)
Received: from [10.1.1.66] (static-dsl-137.87-197-146.telecom.sk [87.197.146.137]) by zimbra.evolveum.com (Postfix) with ESMTPSA id F3B2F536572 for <scim@ietf.org>; Thu, 8 Sep 2022 08:10:45 +0200 (CEST)
Message-ID: <6d9cce85-2b9c-7afc-c198-c93ec37be106@evolveum.com>
Date: Thu, 08 Sep 2022 08:10:44 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: scim@ietf.org
References: <CAKzrJhZ=soh18bXSn7sR=q66mqG=vK0q5ebj4Efx_a2H26V1jQ@mail.gmail.com> <E716D387-EDA3-4BAF-B7DF-65C9F5CC58CC@independentid.com>
From: Radovan Semancik <radovan.semancik@evolveum.com>
In-Reply-To: <E716D387-EDA3-4BAF-B7DF-65C9F5CC58CC@independentid.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/q4mX8cFnpB_AB3gk2BTWHT_wvIg>
Subject: Re: [scim] User extension for not valid before / after ?
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Sep 2022 06:10:55 -0000

Hello,

On 7. 9. 2022 19:19, Phillip Hunt wrote:
> 2. Attribute metadata. This can be things like verification status, 
> expiry, but for attributes. Was this email verified?  When does a role 
> expire? Etc.
>
We have conducted a full end-to-end proof of concept for this, from the 
low-level schema layers all the way to UI. It is very challenging but 
feasible. Surprisingly, the part of the communication protocol and 
data/metadata representation is not that difficult. The most challenging 
parts are the schema, and the implementation of data processing code 
(server/client), and of course, the UI. It is much harder than it seems, 
but it is feasible.

This is a nice summary of the problem and our solution:

https://docs.evolveum.com/midpoint/projects/midprivacy/phases/01-data-provenance-prototype/identity-metadata-in-a-nutshell/

Please see here for all the gory details:

https://docs.evolveum.com/midpoint/projects/midprivacy/phases/01-data-provenance-prototype/

-- 
Radovan Semancik
Software Architect
evolveum.com