Re: [scim] Contributors needed for HR schema

Danny Mayer <mayer@pdmconsulting.net> Mon, 20 June 2022 19:34 UTC

Return-Path: <mayer@pdmconsulting.net>
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 BFD1FC159492 for <scim@ietfa.amsl.com>; Mon, 20 Jun 2022 12:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.982
X-Spam-Level:
X-Spam-Status: No, score=-2.982 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.876, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 xbN989wj2C9e for <scim@ietfa.amsl.com>; Mon, 20 Jun 2022 12:34:05 -0700 (PDT)
Received: from chessie.everett.org (unknown [IPv6:2001:470:1:205::234]) (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 71BB2C14CF14 for <scim@ietf.org>; Mon, 20 Jun 2022 12:33:58 -0700 (PDT)
Received: from [192.168.1.193] (pool-108-26-223-182.bstnma.fios.verizon.net [108.26.223.182]) (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 chessie.everett.org (Postfix) with ESMTPSA id 4LRfw35kDLzMNrC; Mon, 20 Jun 2022 19:33:55 +0000 (UTC)
Content-Type: multipart/alternative; boundary="------------LfiNeVhyzx2ATT51LETpo9bk"
Message-ID: <76b2c137-9ae4-74ab-0482-80328a7db032@pdmconsulting.net>
Date: Mon, 20 Jun 2022 15:33:54 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Danny Zollner <Danny.Zollner=40microsoft.com@dmarc.ietf.org>, "scim@ietf.org" <scim@ietf.org>
References: <MN2PR00MB0720A50B2E5EB355A07E5714FFAF9@MN2PR00MB0720.namprd00.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <MN2PR00MB0720A50B2E5EB355A07E5714FFAF9@MN2PR00MB0720.namprd00.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/sxTRikvwLoQebhVOB_TBebuzTIQ>
Subject: Re: [scim] Contributors needed for HR schema
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: Mon, 20 Jun 2022 19:34:11 -0000

I have plenty of experience fetching non-privacy data from HR. The 
bigger question, as usual is how much do you want to make "public" in 
other applications and how do you make sure you limit the data that the 
HR organization is prepared to share with other parts of the company.

Danny

On 6/17/22 4:35 PM, Danny Zollner wrote:
>
> Hi SCIM-ers,
>
> One of the items on the charter for the SCIM working group is to 
> design a human resources-centric schema for SCIM. For this to be 
> successful, we’ll need contributors that are knowledgeable on HR and 
> HCM services and concepts. If anyone has background on this area – 
> ideally previously or currently working for an organization involved 
> in this space – and can contribute, please respond to this thread and 
> let us know of your interest.
>
> I’ve had some discussions with folks more knowledgeable on these sort 
> of things than I am already, and here are a few things I took away 
> from that that I’d like to put out there as ideas up for discussion:
>
>  1. We should create a new resource, “Worker”, rather than make an HR
>     schema on a user resource. HR data is likely to feed into a logic
>     engine of some sort that then ultimately decides what needs to
>     happen, and HR systems generally should not be directly turning HR
>     data into users in other systems without some middle layer.
>
>  2. Some attributes in this schema may have a finite list of
>     acceptable values – think locations, departments, cost centers.
>     Extending other new resources, i.e.: /CostCenters, may be helpful
>     for discovery’s sake to allow a client interacting with an HR/HCM
>     SCIM service provider to GET a list of allowed locations,
>     departments, cost centers, etc.. and more efficiently generate
>     requests where the values of these attributes can be predetermined
>     to be valid or not ahead of an operation to create/update a worker.
>
> Thanks,
>
> Thanks,
>
> Danny Zollner
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim