[scim] Completed review of SCIM Profile for Security Event Tokens
Arie <arietimmerman@gmail.com> Thu, 21 December 2023 11:29 UTC
Return-Path: <arietimmerman@gmail.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 1314FC0900AD for <scim@ietfa.amsl.com>; Thu, 21 Dec 2023 03:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.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 ro-NbBm7W-QE for <scim@ietfa.amsl.com>; Thu, 21 Dec 2023 03:29:18 -0800 (PST)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 60F5EC090372 for <scim@ietf.org>; Thu, 21 Dec 2023 03:29:18 -0800 (PST)
Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-dbd99c08cd6so722442276.0 for <scim@ietf.org>; Thu, 21 Dec 2023 03:29:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703158157; x=1703762957; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=VrBgSdsMZboa1BFQcjrTFLf3sEL96PycMs1v9tQmzYM=; b=Hr0d3IiI4KYHpxAhRf5j4UwT3/elQkUxp54VGCCqDQezgf1c4A9gq4D2GzkAAsMCYA fhfwiGU8m2aRic9j6nBTB8EEv4pgZOEy2OGI3jjpL3H+/BuzNNCYBs9PIRn4Zka+lcP0 WUOFAu2S8gMNnS3PZwI6Lz0HjnsKNKF9EFC9bliY/oR3YeVoBGQV3SksD7/oygbmIgMm rp3+LE/aji9+gjoEAV3pSE06AEZ1YgaKGFfGU7AloR12INBfohvCSkkoFlAEinapjk9/ 1VMFGSCQxpo4Pe1/c91fb86qzYy8Mf47EzajLAIcUpRdjT7oe7G3VUydaf6QUQGFefyH 7tgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703158157; x=1703762957; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VrBgSdsMZboa1BFQcjrTFLf3sEL96PycMs1v9tQmzYM=; b=sKZdYLHkWEYSX67K7cesBXrM/skeJRoA7JRnK/QdxrOGW4qtouKmd02vo8pjZZ161x cK2HD+pJ+3N6CMjQAT93yFUA9sIMQPOm6K4ezY9TzzDoYWJLiHpa2wrlQL1tRt2zSOxf j0fl1ZXr4JHgiHTSwrzVA9T8s0C4HHH4WIMze0vMVMIv771/9imxZb36LjIT4tjlcIut kc/PmG6IN5KWgxcM2bVevVermWsIE7WEBx9BGimZgpPkpj1e0ZeHY0fs1NWu+Hi0gQBl 6+TaLhNNhKADlFfZSf8O7EK3e1x3EM3erP9e8VcT7wPb3U8UNUnEAMAjanP+NuKvkX2L SQtg==
X-Gm-Message-State: AOJu0Yz0rL4843GO+xQL9bFJmVk8RskAtmg9M5Jp7mZL9lr6Dw3sctTV 51ONKizbgI72c8Vf0v+VbtqlxO/eG3WNryikt2TitYKduVbs8w==
X-Google-Smtp-Source: AGHT+IHVOPbqVmPfJ5oVsmduvBQSAIekMdZYveoDfgWT89eVheIJ/9KDVEVETz7OGsCXIGmjrE0tJ8r5gqeAcrdTgas=
X-Received: by 2002:a05:6902:2002:b0:dbd:467e:415d with SMTP id dh2-20020a056902200200b00dbd467e415dmr1342829ybb.81.1703158157225; Thu, 21 Dec 2023 03:29:17 -0800 (PST)
MIME-Version: 1.0
From: Arie <arietimmerman@gmail.com>
Date: Thu, 21 Dec 2023 12:29:05 +0100
Message-ID: <CANL9WzhF4QK8J+t6Guj1GbFyMCaY8XGixDzHMr1PW7gTRri-hQ@mail.gmail.com>
To: scim@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f53333060d036805"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/7CRwoVZoOetOGxa5S8ff0jCT0t8>
Subject: [scim] Completed review of SCIM Profile for Security Event Tokens
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, 21 Dec 2023 11:29:23 -0000
Hi All, While implementing the SCIM Profile for SET I stumbled upon a few minor challenges/issues. * Relative path in sub_id.urn while absolute paths seems more common * It should be allowed to include touched attributes instead of changed attributes for notice events * version attributes are not explained Issues have been created at https://github.com/ietf-scim-wg/draft-ietf-scim -events. In case you are interested, a minimal yet functioning implementation of SCIM Profile for Security Event Tokens and RFC8936 (SET delivery via HTTP, polling) can be found here: https://scim.dev/playground/securityeventtoken/ Regards, Arie Timmerman